User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008012508 Fedora/3.0b3pre-0.beta2.12.nightly20080121.fc9 Minefield/3.0b3pre Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008012508 Fedora/3.0b3pre-0.beta2.12.nightly20080121.fc9 Minefield/3.0b3pre Accessing <https://evalcyt.conicyt.cl/declaracion-astronomia>, Firefox crashes and gives a backtrace. I have two saved usernames + passwords on this site, trying to enter the username (either from the pulldown menu or by hand) gives a crash. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 300733 [details] Resulting gecko-bugreport.txt file, zipped The gecko-bugreport.txt file that results, zipped.
We accept only bug reports from official Mozilla.org builds. Please provide a Breakpad id of this crash. Send the breakpad crash with the latest nightly and look in "about:crashes" for the id.
(In reply to comment #2) > We accept only bug reports from official Mozilla.org builds. Bull. Tell that to anyone who cvs pulls and builds from source on their own then. Like you know, a bunch of developers. I'm only doing cvs pulls and builds. I'm trying to _help_ by providing extra builds on linux of cvs snapshots to people. Reporting bugs directly here is important. Please treat this as normal.
There are reasons for this. Many vendors are adding additional patches. How should we fix such bug, the bug reports will just stay unconfirmed in bugzilla for years. Just look at bug bug 415090 for an example with a bug in a SuSe build. Bug reports from the official source are of course valid, you can use only different build options and a different compiler in that case.
caillon: you're going to need to provide facilities for them to get useful stack traces. we do not have the ability to handle the provided stack trace. when developers build from cvs (or hg or some other random system), we expect them to provide valid/useful stack traces. if they don't, we yell at them too. does something prevent you from providing a working crash reporter server? reporter: offhand, i'd have filed this in password manager. however your steps to reproduce are bad, please read about how to file a bug. steps should be: 1. create a new profile 2. load https://evalcyt.conicyt.cl/declaracion-astronomia 3. log in 4. when the log in succeeds, click the info banner to save the password 5. quit 6. run again (using the profile from 1) 7. load https://evalcyt.conicyt.cl/declaracion-astronomia 8. log in using account 2 9. when the log in succeeds, click the info banner to save the password 10. quit 11. run again (using the profile from 1) 12. load https://evalcyt.conicyt.cl/declaracion-astronomia 13. enter one character from one of the two usernames (from 3/8) 14. click on the username 15. click Ingresar 16. at some point here, firefox crashes note: these steps aren't complete, your steps should be, you should indicate each time focus changes from field to field and how, if you click, press tab, press enter, or sneeze, that should be documented. if you press the down arrow, or the up arrow, or backspace, that should be documented. and you really should test with a new profile (see step 1). we don't stick in a steps to reproduce field for nothing (nor a url field, which you left blank). and steps to reproduce shouldn't lie, you said that you crashed loading https://evalcyt.conicyt.cl/declaracion-astronomia/, but you then later go on to say that you selected a previously saved login. we do welcome new contributors, but we ask that you follow the instructions. http://www.mozilla.org/support/firefox/bugs http://developer.mozilla.org/en/docs/Bug_writing_guidelines http://www.mozilla.org/bugs/
The attached bugreport isn't useful, it's a bunch of hex and generic process info, so I'm not sure what to do with it. A breakpad report or stack from a debug build would be far more useful. Timeless: were you able to recreate the crash with those steps, or is that just an example?
sorry, that was an incomplete example of how to write /almost/ useful steps. if i had actually reproduced them, i'd have included an incident id or stack trace and confirmed this bug.
Horst, to get a useful stacktrace from the Fedora build, you'll need to install the xulrunner-debuginfo (and probably firefox-debuginfo) packages and grab a stacktrace from gdb: firefox -g -d gdb (gdb) run [make firefox crash] (gdb) bt please attach the output of bt to this bug.
from https://bugzilla.redhat.com/show_bug.cgi?id=430981#c9 Comment #9 From Horst H. von Brand on 2008-01-31 21:09 EST [reply] Fixed in firefox-3.0-0.beta2.15.nightly20080130.fc9.i386