Description of problem: I run Chatzilla for the first time (i.e. profile was not existing before) I opened Freenode Joined #plone, #zato and #quintagroup channels Then moved mouse button over menu and possibly even clicked it. This is the most fuzzy part. Application crashed. Subsequent application launch didn't repeat the issue, but revealed some rendering issue with menu. I.e, visually the ChatZilla menu has black background intead of grey, Other menus does not have background at all and thus the menu items are rendered on transparent background. This potentially can be connected with OpenChrome X drivers for the VIA graphics. Version-Release number of selected component: xulrunner-26.0-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/lib/xulrunner/xulrunner -app /usr/share/chatzilla-0.9.87/application.ini --chat irc:// crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib/xulrunner/xulrunner kernel: 3.12.6-300.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #2 nsProfileLock::FatalSignalHandler at /usr/src/debug/xulrunner-26.0/mozilla-release/profile/dirserviceprovider/src/nsProfileLock.cpp:180 #3 AsmJSFaultHandler at /usr/src/debug/xulrunner-26.0/mozilla-release/js/src/jit/AsmJSSignalHandlers.cpp:963 #5 mozalloc_abort at /usr/src/debug/xulrunner-26.0/mozilla-release/memory/mozalloc/mozalloc_abort.cpp:30 #6 Abort at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/base/nsDebugImpl.cpp:431 #7 NS_DebugBreak at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/base/nsDebugImpl.cpp:418 #8 X11Error at /usr/src/debug/xulrunner-26.0/mozilla-release/toolkit/xre/nsX11ErrorHandler.cpp:157 #9 ?? #10 ??
Created attachment 850971 [details] File: backtrace
Created attachment 850972 [details] File: cgroup
Created attachment 850973 [details] File: core_backtrace
Created attachment 850974 [details] File: dso_list
Created attachment 850975 [details] File: environ
Created attachment 850976 [details] File: limits
Created attachment 850977 [details] File: maps
Created attachment 850978 [details] File: open_fds
Created attachment 850979 [details] File: proc_pid_status
Created attachment 850980 [details] File: var_log_messages
Yes, it looks like a X error, the crash is related to X resources: #5 mozalloc_abort (msg=0xbfe24210 "###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /builddir/build/BUILD/xulrunner-26.0/mozilla-release/toolkit/xre/nsX11ErrorHandler.cpp, line 157") at /usr/src/debug/xulrunner-26.0/mozilla-release/memory/mozalloc/mozalloc_abort.cpp:30 No locals. #6 0x4f5048ae in Abort (aMsg=<optimized out>) at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/base/nsDebugImpl.cpp:431 No locals. #7 NS_DebugBreak (aSeverity=3, aStr=0x8e0b4c18 "X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago", aExpr=0x0, aFile=0x4fa5490d "/builddir/build/BUILD/xulrunner-26.0/mozilla-release/toolkit/xre/nsX11ErrorHandler.cpp", aLine=157) at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/base/nsDebugImpl.cpp:418 buf = {buffer = "###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /builddir/build/BUILD/xulrunner-26.0/mozilla-release/toolkit/xre/nsX11ErrorHandler.cpp, line 157\000\000\000\000"..., curlen = 196} ll = <optimized out> sevString = <optimized out> Can you reproduce it regularly? And do you see it with other drivers, like vesa?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days