User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0a1) Gecko/20110905 Firefox/9.0a1
Build ID: 20110905030839
Steps to reproduce:
Trying to login to localhost web admin interface of Software Kiwi Syslog Server, that is available only for licensed users.
For info http://www.kiwisyslog.com/kiwi-syslog-server-overview/
Crash report: https://crash-stats.mozilla.com/report/index/bp-a0cb2631-75b5-4408-a2de-0e0d32110905
Software version used to report the problem was the latest to current date: 9.2.1
Ooops, the right crash report url is that one: https://crash-stats.mozilla.com/report/index/bp-e14e300f-4008-46a0-94d6-4256f2110905
Oh better, both are correct, but first one if from my current profile and second one is a new clean profile.
The crash occur exactly after submit the login form.
TinyButStrong, since the login screen sounds like it's not easily accessible to others, could you use http://harthur.github.com/mozregression/ in order to determine when this bug was introduced?
Good build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2011-09-04-03-08-22-mozilla-central/
Bad build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2011-09-05-03-08-39-mozilla-central/
Looks like a regression from bug 670493.
TinyButStrong, do you mind testing this build: ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds/jaegermonkey-win32/1315303914/ ? Just to make sure the problem has not been fixed already on the JM branch. Thanks in advance.
Yeah, today build fixed it. Lets mark as resolved.
(In reply to TinyButStrong from comment #8)
> Yeah, today build fixed it. Lets mark as resolved.
Thanks! Just so I understand correctly, the build I linked to in comment 7 works OK and the latest mozilla-central nightly still crashes, right?
I will close this bug when crash-stats.mozilla.com confirms that all js_ValueToBoolean crashes are gone. Just in case there's another bug here :)
My bad, you are right, mozilla-central still crashes.
I will use an alternative syslog server meanwhile.
Thanks to assist me.
*** Bug 685081 has been marked as a duplicate of this bug. ***
Crash-stats confirms that this has been fixed (and I can no longer reproduce bug 685081):
Due to dependencies, qa-. Can someone who is already set up to reproduce this bug please verify the fix? Thanks