[Bug 746647] New: tracker-miner-firefox causes segmentation fault in firefox 10.0
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c0 Summary: tracker-miner-firefox causes segmentation fault in firefox 10.0 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla@forge.provo.novell.com ReportedBy: cfarrell@suse.com QAContact: qa@suse.de Found By: --- Blocker: --- backtrace is below. When I zypper rm tracker-miner-firefox, firefox worked again. paddy:~ # rpm -qi tracker-miner-firefox Name : tracker-miner-firefox Version : 0.12.5 Release : 3.4.1 Architecture: i586 Install Date: Mon Feb 13 09:29:08 2012 Group : System/GUI/GNOME Size : 20570 License : GPLv2+ Signature : RSA/SHA256, Sun Oct 30 08:15:33 2011, Key ID b88b2fd43dbdc284 Source RPM : tracker-extras-0.12.5-3.4.1.src.rpm Build Date : Sun Oct 30 08:14:50 2011 Build Host : build08 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://projects.gnome.org/tracker/ Summary : Tracker miner to index Firefox bookmarks Description : Tracker is a powerful desktop-neutral first class object database, tag/metadata database, search tool and indexer. This package contains a Firefox extension that will index Firefox bookmarks. Distribution: openSUSE 12.1 Program received signal SIGSEGV, Segmentation fault. JS_SetContextThread (cx=0x0) at /usr/src/debug/mozilla/js/src/jsapi.cpp:6276 6276 JS_AbortIfWrongThread(cx->runtime); (gdb) bt #0 JS_SetContextThread (cx=0x0) at /usr/src/debug/mozilla/js/src/jsapi.cpp:6276 #1 0xb71f3037 in ScopedContextThread (cx=0x0, this=<synthetic pointer>) at /usr/src/debug/mozilla/js/src/ctypes/CTypes.cpp:71 #2 js::ctypes::CClosure::ClosureStub (cif=0xac1b8ce0, result=0xbfffc480, args=0xbfffc410, userData=0x9d34c580) at /usr/src/debug/mozilla/js/src/ctypes/CTypes.cpp:5418 #3 0xb720070c in ffi_closure_SYSV_inner (closure=<optimized out>, respp=0xbfffc48c, args=0xbfffc4a0) at /usr/src/debug/mozilla/js/src/ctypes/libffi/src/x86/ffi.c:384 #4 0xb720298a in ffi_closure_SYSV () at /usr/src/debug/mozilla/js/src/ctypes/libffi/src/x86/sysv.S:188 #5 0xb52bfea5 in g_simple_async_result_complete () from /usr/lib/libgio-2.0.so.0 #6 0x9d0cb85e in tracker_sparql_connection_get_async_co (_data_=0x9d34aee0) at /home/juerg/Code/tracker/tracker/src/libtracker-sparql-backend/tracker-backend.vala:373 #7 tracker_sparql_connection_get_async_co (_data_=0x9d34aee0) at tracker-backend.c:3968 #8 0xb52bfea5 in g_simple_async_result_complete () from /usr/lib/libgio-2.0.so.0 #9 0x9d0ca865 in tracker_sparql_backend_get_internal_async_co (_data_=0x9d350500) at /home/juerg/Code/tracker/tracker/src/libtracker-sparql-backend/tracker-backend.vala:318 #10 0x9d0cabdf in __lambda1_ (_data2_=<optimized out>) at /home/juerg/Code/tracker/tracker/src/libtracker-sparql-backend/tracker-backend.vala:300 #11 ___lambda1__gsource_func (self=0x9d34af40) at tracker-backend.c:3176 #12 0xb5b05d10 in g_idle_dispatch (source=0x9be68580, callback=0x9d0cabd0 <___lambda1__gsource_func>, user_data=0x9d34af40) at gmain.c:4785 #13 0xb5b09e2f in g_main_dispatch (context=0xb7b39740) at gmain.c:2425 #14 g_main_context_dispatch (context=0xb7b39740) at gmain.c:2995 #15 0xb5b0a560 in g_main_context_iterate (context=0xb7b39740, block=-1246654640, dispatch=1, self=<optimized out>) at gmain.c:3073 #16 0xb5b0a7fa in g_main_context_iteration (context=0xb7b39740, may_block=0) at gmain.c:3136 #17 0xb6c44e46 in nsAppShell::ProcessNextNativeEvent (this=0xb24d7920, mayWait=false) at /usr/src/debug/mozilla/widget/src/gtk2/nsAppShell.cpp:144 #18 0xb6c5ba2b in nsBaseAppShell::DoProcessNextNativeEvent (this=0xb24d7920, mayWait=false) at /usr/src/debug/mozilla/widget/src/xpwidgets/nsBaseAppShell.cpp:171 #19 0xb6c5bc43 in nsBaseAppShell::OnProcessNextEvent (this=0xb24d7920, thr=0xb7bec520, mayWait=<optimized out>, recursionDepth=0) at /usr/src/debug/mozilla/widget/src/xpwidgets/nsBaseAppShell.cpp:324 #20 0xb6db60f5 in nsThread::ProcessNextEvent (this=0xb7bec520, mayWait=false, result=0xbfffc78f) at /usr/src/debug/mozilla/xpcom/threads/nsThread.cpp:595 #21 0xb6d85079 in NS_ProcessNextEvent_P (thread=<optimized out>, mayWait=false) at /usr/src/debug/obj/xpcom/build/nsThreadUtils.cpp:245 #22 0xb6d0cbb0 in mozilla::ipc::MessagePump::Run (this=0xb7bf5940, aDelegate=0xb7b4e690) at /usr/src/debug/mozilla/ipc/glue/MessagePump.cpp:110 #23 0xb6dd87ee in MessageLoop::RunInternal (this=0xb7b4e690) at /usr/src/debug/mozilla/ipc/chromium/src/base/message_loop.cc:208 #24 0xb6dd8916 in RunHandler (this=0xb7b4e690) at /usr/src/debug/mozilla/ipc/chromium/src/base/message_loop.cc:201 #25 MessageLoop::Run (this=0xb7b4e690) at /usr/src/debug/mozilla/ipc/chromium/src/base/message_loop.cc:175 #26 0xb6c5b682 in nsBaseAppShell::Run (this=0xb24d7920) at /usr/src/debug/mozilla/widget/src/xpwidgets/nsBaseAppShell.cpp:189 #27 0xb6b0ccbf in nsAppStartup::Run (this=0xb24d8a90) at /usr/src/debug/mozilla/toolkit/components/startup/nsAppStartup.cpp:228 #28 0xb62beb9f in XRE_main (argc=1, argv=0xbfffefa4, aAppData=0xb7b1f800) at /usr/src/debug/mozilla/toolkit/xre/nsAppRunner.cpp:3551 #29 0x08049aae in do_main (argv=0xbfffefa4, argc=1, exePath=0xbfffceec "/usr/lib/firefox/libxpcom.so") at /usr/src/debug/mozilla/browser/app/nsBrowserApp.cpp:198 #30 main (argc=1, argv=0xbfffefa4) at /usr/src/debug/mozilla/browser/app/nsBrowserApp.cpp:281 (gdb) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c1 --- Comment #1 from Ciaran Farrell <cfarrell@suse.com> 2012-02-13 08:36:16 UTC --- paddy:~ # rpm -qi MozillaFirefox Name : MozillaFirefox Version : 10.0 Release : 2.17.3 Architecture: i586 Install Date: Mon Feb 13 09:04:25 2012 Group : Productivity/Networking/Web/Browsers Size : 34357979 License : MPL-1.1 or GPL-2.0+ or LGPL-2.1+ Signature : RSA/SHA256, Fri Feb 10 16:05:05 2012, Key ID b88b2fd43dbdc284 Source RPM : MozillaFirefox-10.0-2.17.3.src.rpm Build Date : Wed Feb 8 14:38:56 2012 Build Host : build35 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.mozilla.org/ Summary : Mozilla Firefox Web Browser Description : Mozilla Firefox is a standalone web browser, designed for standards compliance and performance. Its functionality can be enhanced via a plethora of extensions. Distribution: openSUSE 12.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c2 Jon Nelson <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jnelson-suse@jamponi.net --- Comment #2 from Jon Nelson <jnelson-suse@jamponi.net> 2012-02-14 03:51:11 UTC --- Same here. Furthermore, after update, I'm *constantly* being hit by weird extension issues. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c3 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang@rosenauer.org AssignedTo|bnc-team-mozilla@forge.prov |bnc-team-gnome@forge.provo. |o.novell.com |novell.com --- Comment #3 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-14 07:25:46 UTC --- Reassigning to tracker maintainers. Is there any incompatibility known between tracker from 12.1 and FF10? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c4 --- Comment #4 from Vincent Untz <vuntz@suse.com> 2012-02-14 08:04:17 UTC --- (for reference, the code of the extension hasn't changed at all in git, compared to what is in 12.1) I'm not aware of any issue there. But I'm actually surprised it's enabled (I see it's enabled in my FF on Factory too). The extension has this: <em:targetApplication> <Description> <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id> <!-- Firefox --> <em:minVersion>4.0</em:minVersion> <em:maxVersion>6.0.*</em:maxVersion> </Description> </em:targetApplication> Shouldn't it be disabled on Firefox 10 with such a max version? Oh, reading https://addons.mozilla.org/en-US/firefox/pages/appversions/ it seems that 6.0.* is not supposed to be supported and 6.* should be used. Could it be the issue? (Sounds weird that 6.0.* doesn't work, though) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c5 --- Comment #5 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-14 08:11:21 UTC --- 6.0.* would work as well. What changed with Firefox 10 is that it assumes that all addons are compatible to make the fast update cycle smoother and because it's often true for non-binary addons. Does tracker have binary components for the addon? If so something might be wrong with FF addon mechanisms. I had expected that binary addons are recognized and not enabled by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c6 --- Comment #6 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-14 08:20:27 UTC --- Checked myself. It has no binary components so Firefox tries to use it even if the maxVersion is not allowing it. So far it's a feature. So I'm a bit confused how the tracker backend can crash Firefox itself with that stacktrace. Reporters, did you get offered to send the crash data to Mozilla? Could you probably do that once? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c7 --- Comment #7 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-14 08:24:21 UTC --- (In reply to comment #6)
Reporters, did you get offered to send the crash data to Mozilla? Could you probably do that once?
Asking this because I cannot reproduce the crash here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c8 --- Comment #8 from Vincent Untz <vuntz@suse.com> 2012-02-14 08:26:56 UTC --- Well, it has no binary components but it uses ctypes to open a library and call it (see bindings.js). So that could be a weird edge case? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c9 --- Comment #9 from Ciaran Farrell <cfarrell@suse.com> 2012-02-14 08:44:06 UTC --- (In reply to comment #7)
(In reply to comment #6)
Reporters, did you get offered to send the crash data to Mozilla? Could you probably do that once?
Asking this because I cannot reproduce the crash here.
I did use the crash dialog to send the information to Mozilla. However, as far as I remember, this was _before_ I installed the -debuginfo packages to get a backtrace using gdb. Should I crash Firefox again by installing tracker-miner-firefox and hope that the info Mozilla automatically receives is better because of the debuginfo packages? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c10 --- Comment #10 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-14 08:55:35 UTC --- To report a useful crash to Mozilla you do not need the debuginfo packages since decoding happens on server side. I'm behind on updating the server debuginfo information though. I'll ping back when it's good to crash ;-) Stay tuned. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c11 --- Comment #11 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-15 13:52:43 UTC --- all debug information is up for the crash collector (including FF10.0.1 so if you got that already it's fine). Please just make the browser crash one time and submit the crash report and let me know the crash id (which can at least be found in about:crashes afterwards). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c12 --- Comment #12 from Ciaran Farrell <cfarrell@suse.com> 2012-02-15 19:59:04 UTC --- https://crash-stats.mozilla.com/report/index/1cf3d99e-8a27-4892-832a-1fe6f21... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.mozilla.or | |g/show_bug.cgi?id=727745 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c13 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Firefox |GNOME --- Comment #13 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2012-02-16 19:31:17 UTC --- Vincent, there is an analysis in the Mozilla bug. See below. Could you please fix and/or upstream this? ----- Oh, so the extension isn't actually holding onto the closure it passes into native code. So the relevant data gets GCed, and it crashes. The culprit line is here: http://git.gnome.org/browse/tracker/tree/src/plugins/firefox/chrome/content/... The closure is constructed with |tracker.AsyncReadyCallback.ptr(callback_closure)|, which passes it directly into the native function without storing a reference to it. The best solution is probably to do something like: tracker.readyCallback = tracker.AsyncReadyCallback.ptr(callback_closure) tracker.connection_open_async(null, tracker.readyCallback, null); I've updated the docs to add an explicit warning to this effect: https://developer.mozilla.org/en/js-ctypes/js-ctypes_reference/Callbacks Wolfgang, can you take charge of coordinating with the gnome developers to get this fixed? ----- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.gnome.org/ | |show_bug.cgi?id=670251 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c14 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #14 from Vincent Untz <vuntz@suse.com> 2012-03-09 15:11:15 UTC --- Fixed with sr#108653. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c15 --- Comment #15 from Bernhard Wiedemann <bwiedemann@suse.com> 2012-03-09 17:00:32 CET --- This is an autogenerated message for OBS integration: This bug (746647) was mentioned in https://build.opensuse.org/request/show/108653 12.1 / tracker -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746647 https://bugzilla.novell.com/show_bug.cgi?id=746647#c16 --- Comment #16 from Swamp Workflow Management <swamp@suse.de> 2012-04-02 11:10:34 UTC --- openSUSE-RU-2012:0453-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 745977,746647 CVE References: Sources used: openSUSE 12.1 (src): tracker-0.12.5-3.6.1, tracker-extras-0.12.5-3.6.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com