All users were logged out of Bugzilla on October 13th, 2018
Seen while reviewing crash stats. http://tinyurl.com/48kev9u links to the current B12 crashes. Apparently the comments indicate users cannot use slingbox player with new Firefox beta version. Frame Module Signature [Expand] Source 0 libobjc.A.dylib objc_msgSend_stret 1 SlingPlayer SlingPlayer@0x2304c 2 SlingPlayer SlingPlayer@0x9d44 3 SlingPlayer SlingPlayer@0xc7c1 4 SlingPlayer SlingPlayer@0x1eacc 5 XUL nsNPAPIPluginInstance::SetWindow modules/plugin/base/src/nsNPAPIPluginInstance.cpp:467 6 XUL DoStopPlugin layout/generic/nsObjectFrame.cpp:6839 7 XUL nsStopPluginRunnable::Run layout/generic/nsObjectFrame.cpp:2869 8 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:633 9 XUL NS_ProcessPendingEvents_P nsThreadUtils.cpp:200 10 XUL nsBaseAppShell::NativeEventCallback widget/src/xpwidgets/nsBaseAppShell.cpp:132 11 XUL nsAppShell::ProcessGeckoEvents widget/src/cocoa/nsAppShell.mm:399 12 CoreFoundation __CFRunLoopDoSources0 13 CoreFoundation __CFRunLoopRun 14 CoreFoundation CFRunLoopRunSpecific 15 CoreFoundation CFRunLoopRunInMode 16 HIToolbox RunCurrentEventLoopInMode 17 HIToolbox ReceiveNextEventCommon 18 HIToolbox BlockUntilNextEventMatchingListInMode 19 AppKit _DPSNextEvent 20 AppKit -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 21 AppKit -[NSApplication run] 22 XUL nsAppShell::Run widget/src/cocoa/nsAppShell.mm:746 23 XUL nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:220 24 XUL XRE_main toolkit/xre/nsAppRunner.cpp:3766 25 firefox-bin main browser/app/nsBrowserApp.cpp:158 26 firefox-bin firefox-bin@0xa05 27 @0x1
Based on this stack I'm guessing that SlingPlayer is trying to mess with the browser's native window or its native view hierarchy. Plugins shouldn't be doing that and it won't work out of process. We should contact the vendor and make them aware of this. We could also block the existing plugin for now if it doesn't work at all, in order to avoid the crash.
Actually, all these crashes happen in 32-bit mode, and seem to be in-process.
I filled out an online form on their site to inform them of the bug and asked to try to get a developer on it.
Adding [@ strlen | asprintf ] since this is the stack that is showing up in the RC crash stats. https://crash-stats.mozilla.com/report/index/bd8ed56f-012b-40fd-bfe8-d71882110311 is the report with a comment related to Sling player.
Summary: [Mac] Firefox 4.0b12 Crash [@ objc_msgSend_stret | SlingPlayer@0x2304c ] → [Mac] Firefox 4.0b12 Crash [@ objc_msgSend_stret | SlingPlayer@0x2304c ][@ strlen | asprintf ]
It is #3 top crasher on Mac OS X in 4.0RC1.
I sent another email to the PR contact on the website.
Heard back from the product manager for Slingbox.com and he is looking into the crashes.
Crash Signature: [@ objc_msgSend_stret | SlingPlayer@0x2304c ] [@ strlen | asprintf ]
The signature [@ objc_msgSend_stret | SlingPlayer@0x2304c ] doesn't appear on any version in the past 4 weeks. The second signature [@ strlen | asprintf ] appears in low volume with 3 crashes on 8.0 total. Removing the top crash keyword.
Crash Signature: [@ objc_msgSend_stret | SlingPlayer@0x2304c ] [@ strlen | asprintf ] → [@ objc_msgSend_stret | SlingPlayer@0x2304c ] [@ strlen | asprintf ]
I'm marking this bug as WORKSFORME as bug crashlog signature didn't appear from a long time (over half year) in Firefox.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.