Open Bug 1043115 Opened 11 years ago Updated 3 years ago

infinite loop in _XReply at startup

Categories

(Core :: Graphics, defect)

33 Branch
x86_64
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mozilla.org, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release) Build ID: 20140721115042 Steps to reproduce: Upgraded to firefox_33.0~a2~hg20140722r209110 from the Ubuntu Mozilla Daily PPA, and started Firefox. Actual results: A single Firefox window appeared, with the tab bar visible yet containing only one tab and some graphical artefact in the empty space (looking like a very long stretched tab). Firefox spun on both cores for a long time (over 10 minutes) until killed. Before killing, attached gdb and got the following stack trace: #0 0x00007ffa6b185430 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #1 0x00007ffa6b16a257 in XGetAtomName () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x00007ffa6c06ee64 in gdk_x11_xatom_to_atom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #3 0x00007ffa6c064e96 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #4 0x00007ffa6c066116 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #5 0x00007ffa6c0661be in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #6 0x00007ffa6d3b7e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x00007ffa6d3b8048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x00007ffa6d3b80ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x00007ffa6fbc1dac in nsAppShell::ProcessNextNativeEvent ( this=<optimised out>, mayWait=<optimised out>) at /build/buildd/firefox-33.0~a2~hg20140722r209110/widget/gtk/nsAppShell.cpp:156 #10 0x00007ffa6fbef959 in nsBaseAppShell::DoProcessNextNativeEvent ( this=this@entry=0x7ffa65b5d120, mayWait=mayWait@entry=false, recursionDepth=recursionDepth@entry=0) at /build/buildd/firefox-33.0~a2~hg20140722r209110/widget/xpwidgets/nsBaseAppShell.cpp:140 #11 0x00007ffa6fbefa52 in nsBaseAppShell::OnProcessNextEvent ( this=0x7ffa65b5d120, thr=0x7ffa743ec690, mayWait=false, recursionDepth=0) at /build/buildd/firefox-33.0~a2~hg20140722r209110/widget/xpwidgets/nsBaseAppShell.cpp:286 #12 0x00007ffa6f3117ff in nsThread::ProcessNextEvent (this=0x7ffa743ec690, aMayWait=<optimised out>, aResult=0x7fff3fa4029f) at /build/buildd/firefox-33.0~a2~hg20140722r209110/xpcom/threads/nsThread.cpp:741 #13 0x00007ffa6f2cd997 in NS_ProcessNextEvent (aThread=<optimised out>, aMayWait=aMayWait@entry=false) at /build/buildd/firefox-33.0~a2~hg20140722r209110/xpcom/glue/nsThreadUtils.cpp:265 #14 0x00007ffa6f4be924 in mozilla::ipc::MessagePump::Run (this=0x7ffa65b5f140, aDelegate=0x7ffa74381360) at /build/buildd/firefox-33.0~a2~hg20140722r209110/ipc/glue/MessagePump.cpp:99 #15 0x00007ffa6f4b0093 in RunHandler (this=0x7ffa74381360) at /build/buildd/firefox-33.0~a2~hg20140722r209110/ipc/chromium/src/base/message_loop.cc:222 #16 MessageLoop::Run (this=0x7ffa74381360) at /build/buildd/firefox-33.0~a2~hg20140722r209110/ipc/chromium/src/base/message_loop.cc:196 #17 0x00007ffa6fbef45b in nsBaseAppShell::Run (this=0x7ffa65b5d120) at /build/buildd/firefox-33.0~a2~hg20140722r209110/widget/xpwidgets/nsBaseAppShell.cpp:164 #18 0x00007ffa70506d40 in nsAppStartup::Run (this=0x7ffa5e36a0b0) at /build/buildd/firefox-33.0~a2~hg20140722r209110/toolkit/components/startup/nsAppStartup.cpp:278 #19 0x00007ffa704e7aa3 in XREMain::XRE_mainRun (this=this@entry=0x7fff3fa40510) at /build/buildd/firefox-33.0~a2~hg20140722r209110/toolkit/xre/nsAppRunner.cpp:4013 #20 0x00007ffa704e7cf2 in XREMain::XRE_main (this=this@entry=0x7fff3fa40510, argc=argc@entry=1, argv=argv@entry=0x7fff3fa41a08, aAppData=aAppData@entry=0x7fff3fa40710) at /build/buildd/firefox-33.0~a2~hg20140722r209110/toolkit/xre/nsAppRunner.cpp:4084 #21 0x00007ffa704e7f24 in XRE_main (argc=1, argv=0x7fff3fa41a08, aAppData=0x7fff3fa40710, aFlags=<optimised out>) at /build/buildd/firefox-33.0~a2~hg20140722r209110/toolkit/xre/nsAppRunner.cpp:4298 #22 0x00007ffa756e73c1 in do_main (argc=1, argv=0x7fff3fa41a08, xreDirectory=0x7ffa7434d6c0) at /build/buildd/firefox-33.0~a2~hg20140722r209110/browser/app/nsBrowserApp.cpp:282 #23 0x00007ffa756e6b7c in main (argc=1, argv=0x7fff3fa41a08) at /build/buildd/firefox-33.0~a2~hg20140722r209110/browser/app/nsBrowserApp.cpp:643 The call to _XReply at the top of the trace does not return: (gdb) next Single stepping until exit from function _XReply, which has no line number information. ^CQuit Expected results: Firefox should have started as usual.
Please check if the issue occurs using Firefox in safe mode (with your addons disabled): http://support.mozilla.com/kb/Safe+Mode And on a new, empty profile: http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager
If the above helps, disabling hardware acceleration might be useful. Maybe by putting this into the prefs.js file in your profile: user_pref("layers.acceleration.disabled", true); Also, your build may be different from Mozilla ones. Can you reproduce it with a build from https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ ? Nightly builds are called "mozilla-central"
QA Whiteboard: [bugday-20140728]
Component: Untriaged → Graphics
Flags: needinfo?(mozilla.org)
Product: Firefox → Core
After upgrading to the latest PPA version of Firefox 33, there's an error in related libraries, followed by a segfault: [xcb] Too much data requested from _XRead [xcb] This is most likely caused by a broken X extension library [xcb] Aborting, sorry about that. firefox: ../../src/xcb_io.c:736: _XRead: Assertion `!xcb_xlib_too_much_data_requested' failed. Safe Mode works, but if I disable all add-ons while in Safe Mode and restart in normal mode, the infinite loop recurs. Creating a new profile, or resetting the existing profile, solve the issue, but I lose all history, tabs, bookmarks, and other customisations. Is this likely caused by custom settings in about:config, or some other modifications?
Flags: needinfo?(mozilla.org)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.