Debug version of Prism 1.0b2 for Ubuntu
October 8, 2009 – 10:35 amA number of people have reported crashes when using the Prism 1.0b2 build on Ubuntu. I haven’t been able to reproduce this problem, so I’ve created a debug build for further testing. The first person to get me a usable backtrace of the crash will win: a new car!
Okay, maybe not. But you will surely win the gratitude of scores of Ubuntu Prism fans.
6 Responses to “Debug version of Prism 1.0b2 for Ubuntu”
This is a webapp with ’status=true’ in the webapp.ini
It fails to load the page.
http://pastebin.mozilla.org/677509
This is from the same webapp with ’status=false’. It loaded the first page (zimbra login page), but crashed after logging in to zimbra.
http://pastebin.mozilla.org/677510
This one is from a different webapp (request tracker). It doesn’t load with ’status=true’, but with ’status=false’, it seems to work, until it is closed.
http://pastebin.mozilla.org/677511
If theres any more I can do please let me know.
By Murray Fraser on Oct 19, 2009
Thanks, Murray. I have to admit I’m no wiser after examining your backtraces, since it seems to be crashing in different places each time. Nonetheless, I’ll poke around and see if this will help to figure out what’s going on.
Do these crashes occur consistently in the same places or are they pretty much random? Does the status=true option really make a difference? This should do nothing at all on Linux.
By Matthew Gertner on Oct 21, 2009
The crashes are consistently in the same place.
I use status=true to turn on the status bar at the bottom of the webapp.
With status=false (or no status= line in the webapp), there is no status bar, no ‘menu’ to access the prism options. But the webapp works, until you try to close it, when it crashes too.
By Murray Fraser on Oct 29, 2009
Don’t know if this helps, but ran from the command prompt….
http://pastebin.mozilla.org/684143
By Ken Jones on Nov 16, 2009
From all the evidence I’ve seen, crashing deep in the Mozilla core, I’m not sure this is a Prism bug. I’m going to try pulling the very latest Mozilla trunk and building with that to see if it helps.
By Matthew Gertner on Nov 22, 2009
Thanks Matt, I’ll be eagar to test a new build.
By Murray on Nov 23, 2009