User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20080404 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20080404 Firefox/184.108.40.206 Regardless of what is open or not open, opening a new tab, or using an existing tab to go to www.usaa.com, or usaa.com with http:// or https:// begins a TCP conversation. The status bar flickers with activity as Firefox sends and receives information from usaa.com, and then before anything displays, firefox goes away without throwing an error. The process disappears without a trace. Reproducible: Always Steps to Reproduce: 1. type usaa.com in the address bar. 2. press return. 3. See Firefox go away. Actual Results: Firefox instantly stops running as if kill -9'd. Expected Results: the site should display. Slackware 12.1 : bash-3.1$ uname -a Linux justin-laptop 220.127.116.11-smp #2 SMP Wed Apr 30 13:41:38 CDT 2008 i686 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux Window manager or desktop environment doesn't seem to matter. Happens in windowmaker or in KDE.
Forgot to say this also happens with the latest Firefox 3 in the same environment with the same conditions and steps.
try running it from a shell.... ulimit -c unlimited ./run-mozilla.sh -g -d gdb ./firefox-bin r offhand it sounds like a plugin, you should try disabling them
I don't have debugging symbols. I do get this error whether or not I use gdb, and gdb doesn't give me any more information besides [New Thread 0x??????? (LWP ####). bash-3.1$ ulimit -c unlimited bash-3.1$ firefox The program 'firefox-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 13638 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) bash-3.1$ Have not tried to turn off plugins yet. Will get to it later.
If you're still hitting this after updating X and Firefox, you'll need to build Firefox yourself and use the --sync trick in order to get a useful stack trace. I can help with that if needed.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
usaa doesn't crash for me using Firefox 3.7a1pre on Ubuntu 9.10.
You need to log in before you can comment on or make changes to this bug.