Closed Bug 673023 Opened 13 years ago Closed 10 years ago

[10.7] Firefox crash libobjc (MultiClutchInputManager)

Categories

(Firefox :: General, defect)

7 Branch
x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: marcia, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-6f37392b-50c5-4069-9d30-9857f2110720 .
============================================================= 

Seen while looking at crash stats. https://crash-stats.mozilla.com/report/list?signature=libobjc.A.dylib@0x6d47 links to the reports across all versions.

Someone running 4.0.1 notes "OSX Lion breaks FF4 when swiping 'back'. 2 and 3 finger gestures. Crashed about 15 times tonight already."

https://crash-stats.mozilla.com/report/index/6f37392b-50c5-4069-9d30-9857f2110720

Frame 	Module 	Signature [Expand] 	Source
0 	libobjc.A.dylib 	libobjc.A.dylib@0x6d47 	
1 	MultiClutchInputManager 	MultiClutchInputManager@0x1f25 	
2 	MultiClutchInputManager 	MultiClutchInputManager@0x1a0b 	
3 	AppKit 	AppKit@0x73b22 	
4 	XUL 	-[GeckoNSApplication sendEvent:] 	widget/src/cocoa/nsAppShell.mm:190
5 	AppKit 	AppKit@0x552a 	
6 	XUL 	nsAppShell::Run 	widget/src/cocoa/nsAppShell.mm:769
7 	XUL 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:222
8 	XUL 	XRE_main 	toolkit/xre/nsAppRunner.cpp:3686
9 	firefox-bin 	main 	browser/app/nsBrowserApp.cpp:158
10 	firefox-bin 	firefox-bin@0xa05 	
11 		@0x1
I forgot to add it happens across all versions up to Firefox 6 B2.
Chrome had this, too, see http://crbug.com/90075 for discussion.  We patched it out.
Crash Signature: [@ libobjc.A.dylib@0x6d47] → [@ libobjc.A.dylib@0x6d47] [@ objc_msgSend | MultiClutchInputManager@0x1f25 ]
These crashes appear to be caused by a third-party input manager that's incompatible with Lion (and perhaps also with SnowLeopard):

http://www.macupdate.com/app/mac/27016/multiclutch
http://code.google.com/p/chromium/issues/detail?id=90075#c3

We could adapt Chrome's patch.  But we're not seeing many of these crashes (40 in the last week across all FF versions), and I'm inclined to do nothing unless the numbers start going up.
It would be nice if someone could have al look at this again.
Its very annoying, and I have it sometimes very often.

I have experienced the problem in all versions up to 7.0.1 bp-21bcfec4-5014-4370-8cb2-78f032111019
and 8.0 bp-e09f087c-6208-4986-b88a-2d6952111019

Thanks!
Why not just get rid of the MultiClutchInputManager.  It apparently doesn't work with any apps on OS X 10.7.X.
I have experienced that they are also problems with completely different gestures. The tool jitouch responds on the gesture "index finger hold and middle and ring finger down". Sometimes this gesture is not correcty recognized by jitouch and is passed to firefox, which crashes. Here some reports:
bp-5bbac975-17c5-431e-9744-462762111019
bp-4aa16899-cf4b-46b6-95db-6a6f72111019

It also seems to cause problems then ff is in background: The swipe back gestures are not working in finder when firefox is open. And firefox is just crashed when finder was the active application and I tried the "swipe back with 3 fingers"-gesture there.
None of these crashes would be happening without the MultiClutchInputManager, which is 3rd party software.  Its binary (or binaries) are probably located in your /Library/InputManagers/ directory (or maybe the ~/Library/InputManagers/ directory, under your home directory).  Get rid of it, and you'll no longer see any of this bug's crashes.

If you do still see crashes on gestures, they'll be different crashes, and a different bug.  In that case please open a new bug and CC me on it.

If you keep seeing crashes with MultiClutchInputManager somewhere in the crash stack, then you haven't succeeded in deinstalling/disabling the MultiClutchInputManager.
Many thanks. I thought this ImputManager is directly used by firefox somehow.
After deleting the bundle the problem seems to be fixed on my machine.
https://discussions.apple.com/thread/3424007 also documents this
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.