Bug 895571 - After upgrade from firefox 17 to firefox 18, it often hangs
Summary: After upgrade from firefox 17 to firefox 18, it often hangs
Keywords:
Status: CLOSED DUPLICATE of bug 895197
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-15 14:48 UTC by Adam Miller
Modified: 2013-01-15 15:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-15 15:03:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Miller 2013-01-15 14:48:49 UTC
Description of problem:
Launch firefox, use it for a short time and it becomes unresponsive.

Version-Release number of selected component (if applicable):
firefox-18.0-1.fc18.x86_64

How reproducible:
Every time. I've had to install another browser for the mean time because it is unusable.

Steps to Reproduce:
1. Launch firefox
2. Use it... it doesn't seem to matter what sites I visit and the hang/freeze normally happens when I'm attempting to click on a aspect of the firefox UI as opposed to when I use a website.

  
Actual results:
Freeze/Hang of the UI

Expected results:


Additional info:
I tried running from the command line, this happens often enough that I knew it would crash soon after launching. I received the following output when it hangs:

 (firefox:3978): GLib-GObject-WARNING **: cannot register existing type `GdkWindow'

(firefox:3978): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(firefox:3978): Gdk-CRITICAL **: gdk_window_get_display: assertion `GDK_IS_WINDOW (window)' failed


If there are more debugging steps I can/should follow please let me know and I will happily supply more information.

Comment 1 Jan Horak 2013-01-15 15:03:49 UTC
Looks like dup of 895197.

*** This bug has been marked as a duplicate of bug 895197 ***


Note You need to log in before you can comment on or make changes to this bug.