Comment 14 for bug 1559428
Revision history for this message
| Chris Coulson (chrisccoulson) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
If it's memory corruption, the stack trace isn't particularly useful as it doesn't identify what causes the corruption. It could be literally anything. Has anyone tried running it in valgrind? (you'll need to do that on the desktop)