Closed
Bug 451956
Opened 16 years ago
Closed 15 years ago
browser crash on opening link below [XError 'BadAlloc (insufficient resources for operation)']
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ronne, Unassigned)
References
()
Details
Attachments
(1 file)
32.70 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru,en-US; rv:1.9.0.1) Gecko/2008072612 GranParadiso/3.0.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ru,en-US; rv:1.9.0.1) Gecko/2008072612 GranParadiso/3.0.1 I have open tabs: 1) http://www.google.ru/search?complete=1&hl=ru&lr=&newwindow=1&safe=off&client=firefox-a&rls=org.mozilla:ru,en-US:official&hs=dGC&q=%D0%BA%D0%B0%D0%BA+%D0%B7%D0%B0%D0%B4%D0%B5%D0%BB%D0%B0%D1%82%D1%8C+%D0%BE%D0%BA%D0%BD%D0%BE&start=10&sa=N 2) http://www.lingvisto.org/novgreka/alfabeto.html 3) http://www.mail.ru/ I clicked on link on 3-th tab (middle button of mouse, for opening in new tab), url is http://r.mail.ru/n20268249 Browser is crushed. I run browser again, selected repair session and can reproduse it. If I run from console, I got: bash-3.2$ firefox The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 5860 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.2$ firefox --sync The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 15674 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.) Same thing happened early but I couldn't repeat it. Reproducible: Always Steps to Reproduce: 1. Run browser 2. Open link 3. Actual Results: Browser crush Expected Results: Page is open I didn't get core, although core files is unlimited. bash-3.2$ uname -a Linux zaratustra 2.6.26.3 #12 Thu Aug 21 23:11:26 MSD 2008 i686 Intel(R) Pentium(R) M processor 1.60GHz GenuineIntel GNU/Linux bash-3.2$ LANG=C pacman -Qi firefox Name : firefox Version : 3.0.1-2 URL : http://www.mozilla.org/projects/firefox Licenses : MPL GPL LGPL Groups : None Provides : None Depends On : xulrunner>=1.9.0.1-2 desktop-file-utils mime-types shared-mime-info Optional Deps : None Required By : firefox-i18n firefox-spell-ru Conflicts With : None Replaces : None Installed Size : 3206.45 K Packager : Jan de Groot <jgc@archlinux.org> Architecture : i686 Build Date : Sat Jul 26 16:59:56 2008 Install Date : Sun Jul 27 12:43:18 2008 Install Reason : Explicitly installed Install Script : Yes Description : Standalone web browser from mozilla.org
Firfox for Windows doesn't affected and 2.x doesn't affected too.
Version: unspecified → 3.0 Branch
Comment 3•16 years ago
|
||
Probably there was a giant image or page to render. There is a few of such bugs (search for “BadAlloc”).
Summary: browser crush on opening link below → browser crush on opening link below [XError 'BadAlloc (insufficient resources for operation)']
Comment 4•15 years ago
|
||
Opening these 4 URLs in tabs doesn't cause any problems for me, using Firefox 3.7a1pre on Ubuntu 9.10. Could be a dup of bug 424333.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Summary: browser crush on opening link below [XError 'BadAlloc (insufficient resources for operation)'] → browser crash on opening link below [XError 'BadAlloc (insufficient resources for operation)']
You need to log in
before you can comment on or make changes to this bug.
Description
•