Comment 29 for bug 203413
Revision history for this message
| Emilio Pozuelo Monfort (pochu) wrote | #29 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Upstream has suggested to me this could be Xulrunner's fault. It doesn't have when using Xulrunner 1.8, but he said it could be a different thing, such as locking or threading issues, or even memory corruption...
Alexander, do you know whether this could be Xulrunner's fault? I could try downgrading to an older beta release of xul to see whether this was happening by that time.