287921 - crash [@ libglib-2.0.so.0 + 0x18063] called from nsWindow::SetWindowIconList opening a new window(?) when low on memory

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Tom Williams]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

I was trying to switch tabs (I had 8 - 10 or so open) like I normally do when
Firefox suddenly crashed.  It generated talkback id: TB4632010X

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. I was using Firefox as I normally do, with 8 - 10 tabs open, and while
switching between tabs Firefox crashed.
2.
3.

Actual Results:  
Firefox crashed.

Expected Results:  
Firefox should not crash.

This bug was opened as instructed based on discussion starting at comment #3 in
bug: 287643

https://bugzilla.mozilla.org/show_bug.cgi?id=287643#c3

This bug might be related to bug #275004.

Comment 1

[Adam Hauner]

TB4632010X:
libglib-2.0.so.0 + 0x18063 (0xb7a0d063)
libglib-2.0.so.0 + 0x1834b (0xb7a0d34b)
libpixbufloader-xpm.so + 0x31e3 (0xb6ae81e3)
libpixbufloader-xpm.so + 0x3b71 (0xb6ae8b71)
libgdk_pixbuf-2.0.so.0 + 0x676e (0xb7b0576e)
libgdk_pixbuf-2.0.so.0 + 0x6901 (0xb7b05901)
nsWindow::SetWindowIconList() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/widget/src/gtk2/nsWindow.cpp,
line 2643]
nsWindow::SetDefaultIcon() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/widget/src/gtk2/nsWindow.cpp,
line 2688]
nsWindow::NativeCreate() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/widget/src/gtk2/nsWindow.cpp,
line 2170]
nsWindow::Create() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/widget/src/gtk2/nsWindow.cpp,
line 313]
nsWebShellWindow::Initialize() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/xpfe/appshell/src/nsWebShellWindow.cpp,
line 284]
nsAppShellService::JustCreateTopWindow() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 862]
nsAppShellService::CreateTopLevelWindow() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 727]
nsXULWindow::CreateNewContentWindow() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/xpfe/appshell/src/nsXULWindow.cpp,
line 692]
nsXULWindow::CreateNewWindow() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/xpfe/appshell/src/nsXULWindow.cpp,
line 1716]
nsWindowCreator::CreateChromeWindow2() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/toolkit/xre/nsWindowCreator.cpp,
line 710]
nsWindowWatcher::OpenWindowJS() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp,
line 618]
nsWindowWatcher::OpenWindow() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp,
line 457]
GlobalWindowImpl::OpenInternal() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/dom/src/base/nsGlobalWindow.cpp,
line 710]
GlobalWindowImpl::Open() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/dom/src/base/nsGlobalWindow.cpp,
line 3469]
XPTC_InvokeByIndex()
XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode)() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/js/src/xpconnect/src/xpcwrappednative.cpp,
line 2033]
XPC_WN_CallMethod() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp,
line 1287]
js_Invoke() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/js/src/jsinterp.c,
line 949]
js_Interpret() 
[/builds/tinderbox/Fx-Aviary1.0.1/Linux_2.4.20-28.8_Clobber/mozilla/js/src/jsinterp.c,
line 2993]
...

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Tom Williams]

This problem has not occured in a while and seems to happen more frequently as available RAM decreases and swap use increases.  Since reporting this, I've upgraded from 128MB of RAM to 512MB of RAM and the problem has basically disappeared.

Peace...

Comment 4

[Nickolay_Ponomarev]

Does it happen with the latest versions of Firefox and GTK?

If this indeed happens when there's not enough memory, I guess the stack with GTK symbols GTK would be welcome.

Comment 5

[Tom Williams]

(In reply to comment #4)
> Does it happen with the latest versions of Firefox and GTK?

Sorry for the late response.  This problem hasn't happened in so long, I think it's safe to close this bug report.  I'm now running Firefox 2.0 on Ubuntu 6.10 64-bit.

Peace...

Comment 6

[Adam Guthrie]

Thanks for the update. Please reopen if it happens again. ->WFM.