Comment 19 for bug 490228
Revision history for this message
| Gareth White (gwhite-deactivatedaccount) wrote | #19 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It didn't crash last night using Bazaar 2.0.2 plus Alexander's pyd/pdb, but it wasn't reliably reproducible before so I'll keep trying.
I've attached the stack trace from the original crash dump, using Alexander's pdb file. I'm not completely sure it's correct because the pdb doesn't match the pyd file that crashed, but hopefully it'll help shed some light on the problem.
Unfortunately I don't really have a clear way to reproduce the crash yet. What we've been doing is running a tool to generate dummy data to get an idea of how Bazaar will scale if we decide to use it in production. When running this tool bzr.exe crashes (on average) every few thousand generated revisions. Since we're generating roughly 300 revisions an hour it takes some time to reproduce the crash! (It's faster if we don't generate merges but then the data isn't realistic.)
I can't share the repository because we used a recent snapshot of our (proprietary) codebase as a starting point. It's also quite large (1 GB). If we ran the tool on a dummy codebase to start with it and could still reproduce the problem then I could share both. I'm not sure whether the content of the files, the size of the files or even the number of files (22k) is significant.
Another option is to run the tool on a large public repository (e.g. MySQL) and see if it happens with that.