Description of problem: After I install greasemonkey in a fresh firefox profile, then it crashes on quit (or worse - restart). The Firefox from http://releases.mozilla.org/ is fine in this respect. I'm on KDE-4.9.x on Cauldron x86-64. Version-Release number of selected component (if applicable): Cauldron. How reproducible: Always. Steps to Reproduce: 1. Create a new firefox profile - firefox -no-remote or firefox -profilemanager 2. Tools -> Addons - Install Greasmonkey. 3. Quit Firefox. 4. Run firefox from the command-line and start the new profile 5. File -> Quit. Segfault. I'll try to get a backtrace soon and also investigate other crashing extensions.
Here's the backtrace: [Thread 0x7fffb8fff700 (LWP 24214) exited] [Thread 0x7fffdc8ff700 (LWP 24226) exited] [Thread 0x7fffb7176700 (LWP 24217) exited] [Thread 0x7fffbf2ff700 (LWP 24210) exited] [Thread 0x7fffd85ff700 (LWP 24204) exited] [Thread 0x7fffb4fff700 (LWP 24225) exited] [Thread 0x7fffbb1ff700 (LWP 24212) exited] [Thread 0x7fffbd2fe700 (LWP 24211) exited] [Thread 0x7fffde3ee700 (LWP 24195) exited] [Thread 0x7fffdb81e700 (LWP 24199) exited] Program received signal SIGSEGV, Segmentation fault. _cairo_xlib_shm_surface_mark_active (_shm=0x7fffbc946ff0) at cairo-xlib-surface-shm.c:1022 1022 ev.drawable = display->shm->window; Missing debug package(s), you should install: webkit-debug-1.10.1-1.mga3.x86_64 (gdb) print display $1 = (cairo_xlib_display_t *) 0x7fffe3915000 (gdb) print display->shm $2 = (cairo_xlib_shm_display_t *) 0x0 (gdb) bt #0 _cairo_xlib_shm_surface_mark_active (_shm=0x7fffbc946ff0) at cairo-xlib-surface-shm.c:1022 #1 0x00007ffff37e2e6c in _cairo_xlib_surface_put_shm (surface=0x7fffbbf55c00) at cairo-xlib-surface-shm.c:953 #2 0x00007ffff37de949 in _cairo_xlib_surface_flush (abstract_surface= 0x7fffbbf55c00, flags=0) at cairo-xlib-surface.c:1449 #3 0x00007ffff37b16d3 in _cairo_surface_finish_snapshots (surface= 0x7fffbbf55c00) at cairo-surface.c:994 #4 *INT_cairo_surface_finish (surface=0x7fffbbf55c00) at cairo-surface.c:1052 #5 INT_cairo_surface_finish (surface=0x7fffbbf55c00) at cairo-surface.c:1038 #6 0x00007ffff37dba1c in _cairo_xlib_screen_destroy (display=display@entry= 0x7fffe3915000, info=0x7ffff6c17a60) at cairo-xlib-screen.c:287 #7 0x00007ffff37d69e8 in _cairo_xlib_display_finish (abstract_display= 0x7fffe3915000) at cairo-xlib-display.c:82 #8 0x00007ffff3774b27 in *INT_cairo_device_finish (device=0x7fffe3915000) at cairo-device.c:304 #9 INT_cairo_device_finish (device=device@entry=0x7fffe3915000) at cairo-device.c:290 #10 0x00007ffff37d6a77 in _cairo_xlib_close_display (dpy=0x7ffff6cd2000, codes=<optimized out>) at cairo-xlib-display.c:116 #11 0x00007ffff3014c62 in XCloseDisplay (dpy=0x7ffff6cd2000) at ClDisplay.c:65 ---Type <return> to continue, or q <return> to quit--- #12 0x00007fffef5cd96e in gdk_display_x11_finalize (object= 0x7ffff6ce7190 [GdkDisplayX11]) at gdkdisplay-x11.c:890 #13 0x00007ffff12120b8 in g_object_unref (_object=0x7ffff6ce7190) at gobject.c:3023 #14 0x00007ffff4a97e62 in MOZ_gdk_display_close (display= 0x7ffff6ce7190 [GdkDisplayX11]) at /usr/src/debug/mozilla-release/toolkit/xre/nsAppRunner.cpp:2611 #15 0x00007ffff4a9dc88 in XREMain::XRE_main (this=this@entry=0x7fffffffadd0, argc=argc@entry=2, argv=argv@entry=0x7fffffffd1c8, aAppData=aAppData@entry= 0x614c00 <sAppData>) at /usr/src/debug/mozilla-release/toolkit/xre/nsAppRunner.cpp:3930 #16 0x00007ffff4a9dddd in XRE_main (argc=2, argv=0x7fffffffd1c8, aAppData= 0x614c00 <sAppData>, aFlags=<optimized out>) at /usr/src/debug/mozilla-release/toolkit/xre/nsAppRunner.cpp:3947 #17 0x000000000040267d in do_main (argv=0x7fffffffd1c8, argc=2) at /usr/src/debug/mozilla-release/browser/app/nsBrowserApp.cpp:160 #18 main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/mozilla-release/browser/app/nsBrowserApp.cpp:265 (gdb) (gdb)
Hi all, there's a similar segfault with the Lazarus Form Recover 2.3 installed: https://addons.mozilla.org/en-us/firefox/addon/lazarus-form-recovery/ I don't know if it's the same backtracke, but I can find out. Regards, -- Shlomi Fish
And I'm getting a similar crash in my populated profile with only the StumbleUpon addon enabled. In a fresh profile it does not happen, but I don't have a StumbleUpon account configured there.
Created attachment 3031 [details] backtrace from all the threads. This is a backtrace from all the threads and with webkit-debug installed.
CC: (none) => marja11Assignee: bugsquad => dmorganec
I have just installed greasemonkey in my existing profile and am seeing no problems. Since installing the most recent version of Firefox from updates however, firefox regularly locks on and takes up all my CPU. This happens only if I leave firefox running. It maty be a buggy release. I am hoping that the next update will fix it.
CC: (none) => laidlaws
(In reply to Doug Laidlaw from comment #5) > I have just installed greasemonkey in my existing profile and am seeing no > problems. Since installing the most recent version of Firefox from updates > however, firefox regularly locks on and takes up all my CPU. This happens > only if I leave firefox running. It maty be a buggy release. I am hoping > that the next update will fix it. Sorry, I am talking about Mga2 Official, not Cauldron.
Assignee: dmorganec => bugsquad
Version: Cauldron => 3
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
No issue for me: see Comment 6.