FS#19358 - [firefox] glib memory allocation errors

Attached to Project: Arch Linux
Opened by Byron Clark (byronc) - Tuesday, 04 May 2010, 19:04 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 04 May 2010, 21:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Firefox is crashing frequently after the glib update. I'm seeing this with my normal profile and a clean profile. After each crash, I see a message like this:

% firefox

GLib-ERROR **: gmem.c:137: failed to allocate 187415192932453 bytes
aborting...
zsh: abort (core dumped) firefox


Additional info:
firefox 3.6.3-1
glib2 2.24.1-1

Steps to reproduce:
There seem to be lots of different ways to get this to crash, but here's a simple one:

mv ~/.mozilla ~/.mozilla.old
firefox
In the location bar: type google.com, then try to erase it all with the backspace key.
This task depends upon

Closed by  Ionut Biru (wonder)
Tuesday, 04 May 2010, 21:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  gtk2 2.20.1-2
Comment by Byron Clark (byronc) - Tuesday, 04 May 2010, 19:31 GMT
This is not fixed by rebuilding xulrunner and firefox.
Comment by Byron Clark (byronc) - Tuesday, 04 May 2010, 19:35 GMT
Reverting to glib2 2.24.0-1 also fails to fix the issue.
Comment by Damien (dada) - Tuesday, 04 May 2010, 19:42 GMT
I had this bug too on my x86_64 system since the last update.
I was able to launch the 32 bits version of Firefox from a chroot, but wasn't able at all to use the 64 bits version, cause the error did happen at every Firefox startup.

Then, I deactivated the Cooliris plugin without to uninstall it, and now I can use Firefox. Maybe it will crash again, but it doesn't do it anymore at startup.
Comment by Byron Clark (byronc) - Tuesday, 04 May 2010, 19:45 GMT
@Damien Unfortunately, I'm still seeing the problem running with and empty profile in safe mode (firefox -safe-mode).
Comment by doesntMatter (wasserwasser) - Tuesday, 04 May 2010, 20:13 GMT
i get this error message when starting lxpanel(not useable). x86_64, too.
Comment by Ionut Biru (wonder) - Tuesday, 04 May 2010, 20:19 GMT
that is a bug in gtk2.20.1 introduced by http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-20&id=a0f23e1706b34bca6a65183040d1f1498cce2a50

new packages are uploaded right now
Comment by Byron Clark (byronc) - Tuesday, 04 May 2010, 21:14 GMT
Thanks for the updated gtk2 packages, firefox works great now.

Loading...