crash in hang | libsystem_kernel.dylib@0x114de on limelight.com (playing video using Flash)

RESOLVED INCOMPLETE

Status

()

Core
Plug-ins
--
critical
RESOLVED INCOMPLETE
3 years ago
a year ago

People

(Reporter: stephend, Unassigned)

Tracking

({crash})

37 Branch
x86
Mac OS X
crash
Points:
---

Firefox Tracking Flags

(firefox47 affected, firefox48 affected, firefox-esr45 affected)

Details

(crash signature, URL)

Attachments

(1 attachment)

This bug was filed from the Socorro interface and is 
report bp-af6f33d5-5838-4080-b2e4-8c76f2150304.
=============================================================

STR:

1. Load http://www.limelight.com/services/orchestrate-content-delivery.html
2. Click on the 1st video, just a bit below the fold

Actual Results:

Crash/hang, in:

Frame 	Module 	Signature 	Source
Ø 0 	libsystem_kernel.dylib 	libsystem_kernel.dylib@0x114de 	
Ø 1 	CoreFoundation 	CoreFoundation@0x735b3 	
Ø 2 	CoreFoundation 	CoreFoundation@0x72a7a 	
Ø 3 	CoreFoundation 	CoreFoundation@0x722d7 	
Ø 4 	HIToolbox 	HIToolbox@0x32a1e 	
Ø 5 	HIToolbox 	HIToolbox@0x32799 	
Ø 6 	HIToolbox 	HIToolbox@0x325da 	
Ø 7 	AppKit 	AppKit@0x91620 	
Ø 8 	AppKit 	AppKit@0x90c1f 	
Ø 9 	AppKit 	AppKit@0x86932 	
10 	XUL 	base::MessagePumpNSApplication::DoRun(base::MessagePump::Delegate*) 	ipc/chromium/src/base/message_pump_mac.mm
11 	XUL 	base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*) 	ipc/chromium/src/base/message_pump_mac.mm
12 	XUL 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc
13 	XUL 	XRE_InitChildProcess 	toolkit/xre/nsEmbedFunctions.cpp
14 	plugin-container 	main 	ipc/contentproc/plugin-container.cpp
15 	plugin-container 	start

Hardware Overview:

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro10,1
  Processor Name:	Intel Core i7
  Processor Speed:	2.6 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	6 MB
  Memory:	16 GB
  Boot ROM Version:	MBP101.00EE.B07
  SMC Version (system):	2.3f36

Build ID:  Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0

Adobe Flash:

Version: 16.0.0.305
Shockwave Flash 16.0 r0
You're running FF 37b2?
Can't reproduce with FF 37b2 on OS X 10.8.5 with a non-Retina display.  Later I'll try other versions and configurations.  I tested with a clean profile.

Did you really mean to set this Platform == All?  Have you seen it on Windows or Linux?
OS: All → Mac OS X
Hardware: All → x86
(In reply to Steven Michaud from comment #1)
> You're running FF 37b2?

Yep; 37.0b2

And, sorry; I filed from the Socorro interface, and didn't adjust the pre-filled OS/Platform; fixed, now.
In case it helps, still crashing/hanging, with beta 3 of Firefox 37: https://crash-stats.mozilla.com/report/index/ec78c1ee-2116-4449-afaa-4574e2150306
I can't reproduce on OS X 10.10.2 either (using FF 37b3).

Stephen, please test with a clean profile (and/or in Safe Mode).
(In reply to Steven Michaud from comment #5)
> I can't reproduce on OS X 10.10.2 either (using FF 37b3).
> 
> Stephen, please test with a clean profile (and/or in Safe Mode).

1) Clean profile crash/hang: https://crash-stats.mozilla.com/report/index/bp-63c8e21b-9553-488e-8764-5872b2150309
2) Safe Mode crash/hang: https://crash-stats.mozilla.com/report/index/bp-e1acb873-26dd-4e49-904d-f16572150309
OK, then, please try restarting your computer :-)

I'm not kidding.  Many people (though not I) leave their Macs unrebooted for weeks at a time.  For those people, I've seen rebooting "fix" all kinds of weird problems.

If that doesn't work, please attach the contents of about:support.

And please provide as much information as possible about how you actually trigger these crashes.  I've been following your STR from comment #0 exactly ... but it *is* a little sparse.
Even imitating your video exactly (as best I can manage), I still can't reproduce your hangs.

I notice you're using OS X 10.10.3 -- a pre-release version.  Can you test on a different partition (or machine), running a different version of OS X?
need-info? on myself to take a look at this on Marcia/lab's machines, on Monday.
Flags: needinfo?(stephen.donner)
(In reply to Steven Michaud from comment #9)
> Even imitating your video exactly (as best I can manage), I still can't
> reproduce your hangs.
> 
> I notice you're using OS X 10.10.3 -- a pre-release version.  Can you test
> on a different partition (or machine), running a different version of OS X?

I tested on an older, 10.6.8 machine in the QA lab, with Firefox 37 Beta 4, and couldn't crash or hang that -- the video played just fine for me, immediately.

However, I also installed Developer Edition on my 10.10.3 (upgraded to the latest version, today:   System Version:	OS X 10.10.3 (14D105g)) and with the latest Flash plugin: Version: 17.0.0.134, and got the following results:

* Nightly doesn't crash or hang, but also doesn't play the video
* Developer Edition hangs (but hadn't crash in over 5 minutes, and I had to move on with my testing, so I force-quit it, after taking a screenshot)
* 37 beta 4 crashes, still: https://crash-stats.mozilla.com/report/index/ffff435e-1fa9-4a86-a6a4-bbc612150316
Flags: needinfo?(stephen.donner)
Created attachment 8578360 [details]
Screen Shot of my Developer Edition hang on 10.10.3
No crash for me using Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20150305021524 CSet: 152cd2386c2f and the latest Flash version 17.0.0.134.
(In reply to Marcia Knous [:marcia - use ni] from comment #13)
> No crash for me using Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:36.0)
> Gecko/20100101 Firefox/36.0 ID:20150305021524 CSet: 152cd2386c2f and the
> latest Flash version 17.0.0.134.

Also the video plays fine using the latest Nightly on the same machine, using a clean profile.
At some point I'll install the 10.10.3 Beta (probably in a VM), just to test with it.

But for now it seems likely that this bug only happens with that beta, and is at least partly due to bugs in it.
I am getting a very similar hang/crash the last two days on youtube.com - https://crash-stats.mozilla.com/report/index/721f87aa-ceb0-4295-a2ee-43c852150407. Right now it is 100% reproducible on that site. I am running the latest seed of 10.10.3 and have Flash Version: 17.0.0.134.

Happens with a clean profile as well - any debugging/sampling that will help isolate what might be going on?
In Comment 16 I am running Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0 ID:20150407004006 CSet: 229e75e75ef7
More than half of the current Mac Flash 17.0.0.134 crashes are bug 1146036.  Though your stack, Marcia, doesn't resemble those already listed at bug 1146036, it's possible you're seeing some kind of variant.

In any case, it'll be difficult to test for any other kind of Mac Flash bug in current Flash versions while bug 1146036 remains unfixed -- that bug is likely to overwhelm everything else.
Crash volume for signature 'hang | libsystem_kernel.dylib@0x114de':
 - nightly (version 50): 0 crash from 2016-06-06.
 - aurora  (version 49): 0 crash from 2016-06-07.
 - beta    (version 48): 2 crashes from 2016-06-06.
 - release (version 47): 29 crashes from 2016-05-31.
 - esr     (version 45): 3 crashes from 2016-04-07.

Crash volume on the last weeks:
             Week N-1   Week N-2   Week N-3   Week N-4   Week N-5   Week N-6   Week N-7
 - nightly          0          0          0          0          0          0          0
 - aurora           0          0          0          0          0          0          0
 - beta             0          1          0          0          0          1          0
 - release          8          4          2          5          3          6          1
 - esr              1          0          0          0          0          1          0

Affected platform: Mac OS X
status-firefox47: --- → affected
status-firefox48: --- → affected
status-firefox-esr45: --- → affected

Comment 20

a year ago
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.