14.04 after upgrade freezes with fire fox

[NoOp]

On 11/07/2014 11:22 AM, Linda wrote:
> I upgraded from 12.04 LTS to  14.04 LTS I run this machine with gnome flashblack (Metacity)
> when I run firefox it freezes the machine so you have to turn it off and restart. It ignores the keyboard and you can not even ssh in and kill the processes. I tried running it in a terminal and I get the following error
> GLib-CRITICAL  g-slice-set-config:assertion 'sys-page-siace == 0' failed
> Any ideas on what might be missing or need to be fixed.
>            Linda
> 

Linda, I also run 14.04 flashback with Metacity, and with Compiz - you
might try installing FF directly from Mozilla
<https://www.mozilla.org/en-US/> and running that version. I only run FF
and SeaMonkey Mozilla versions and have not had any problems with
either. Ubuntuzilla's build's are solid as well:
<http://sourceforge.net/p/ubuntuzilla/wiki/Main_Page/> if you'd prefer a
repository version.


Other suggestions:

1. Clear your cache and cookies regularly. Easiest way to do this is to
install Prefbar: <http://prefbar.tuxfamily.org/> you can add buttons to
clear cache, clear cookies, turn off/on Flash Java Javascript etc).

2. Try FF in Safe mode & see if it still freezes. If not, it could be an
add-on/extention that you have installed - turn on your
add-on's/extensions one-by-one to see if you can find the one causing
the issue.

3. Turn off Flash unless you absolutely need it. More often than not
browser issues can be traced back to Flash. Use Prefbar to selectively
turn Flash on/off.

for
GLib-CRITICAL  g-slice-set-config:assertion 'sys-page-siace == 0' failed
See:
<https://bugzilla.mozilla.org/show_bug.cgi?id=672671>
("GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0'
failed" on startup, for version 7 and earlier)
<https://bugzilla.mozilla.org/show_bug.cgi?id=833117>
(Does not disable glib slice allocator with glib >= 2.35. Startup warning.)
Note that most of the comments are against distro supplied versions of
Firefox; so again, you might try the Mozilla version directly & see if
the problem still exists. Either way, you can then subscribe to those
bug reports and add your info (or open/search for an Ubuntu bug report
already in process).