Closed Bug 815231 Opened 13 years ago Closed 13 years ago

Crash when reloading testcase [@ CMIOUnits@0x63e4b ]

Categories

(Core :: WebRTC, defect, P1)

19 Branch
x86
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: whimboo, Assigned: jesup)

References

Details

(Keywords: crash, testcase, Whiteboard: [getUserMedia], [blocking-gum-])

Crash Data

Attachments

(3 files)

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20.0 Firefox/20.0 ID:20121125030729 crashes when attachment 669440 [details] gets opened and reloaded a couple of times. Crash report: bp-1c2c040f-1bcd-467e-bb30-e269c2121126 0 @0x10b6ecb80 1 CMIOUnits CMIOUnits@0x63e4b 2 CMIOUnits CMIOUnits@0x63d95 3 VDC VDC@0x16a73
That attachment BTW is from bug 799419
A quick check with a debug nightly build didn't show up this problem. So it could be only happening for optimized builds.
Tried a debug local inbound build (linux), no crashes. (Did you have the permissions.disabled set to true, or was it asking you each time?) Building an opt build off m-c
Yes, permissions have been disabled.
Reloaded about 100 times on Linux opt build (non-PGO). No failures. (Camera didn't always end up on; there were no debugs to tell me what was happening, but no failures.)
This should be an OS X specific crash. At least given the CMIOUnits entry in the stack, which is part of the CoreMediaIOServices.framework.
Crash Signature: [@ CMIOUnits@0x63e4b ]
I have a mac opt build running a loop of the testcase (reload 2 seconds after load) now. I'll let it run, but I'm probably over 100 iterations so far. This is a local opt build from inbound. (Are mac builds PGO'd?)
Ok, mac locked up (perhaps trying to hibernate while playing with the camera). After re-trying, I got it to fail eventually in an opt build. I'll try again with a debug build. You get a lot of errors like this: in many spurts, which may also be a symptom of the same bug that causes the crash. I got 15000 lines of those over 1/2 hour before it crashed, typically 10-20 (sometimes more) from a specific iteration of the code, maybe 5 seconds apart. It also might be related to the camera working for one iteration (light on), then not working for the next (light off), with ~2 seconds per iteration plus overhead, which roughly matches the pacing of the errors. Tue Nov 27 13:05:43 2012 CMIO_Graph.cpp:8709:HandleRenderNotify CMIOGraph::HandleRenderNotify() called but graph is not initialized!
So I got it to crash in a related way (again CMIOUnits/CoreMedia) on Debug. I'll also upload the modified testcase. This time thread 0 crashed.
Priority: -- → P1
Whiteboard: [getUserMedia], [blocking-gum+]
Assignee: nobody → rjesup
Flags: in-testsuite?
Note: this took an hour+ of constant reloads to trigger the problem. Probably should be retested given how long since it was reproduced, and the number of changes we've made - especially regarding cleanup on reload.
If it's easy to hit on retest we can make it blocking+ again; given it's in the OS drivers and how hard, blocking-
Whiteboard: [getUserMedia], [blocking-gum+] → [getUserMedia], [blocking-gum-]
(In reply to Randell Jesup [:jesup] from comment #13) > If it's easy to hit on retest we can make it blocking+ again; given it's in > the OS drivers and how hard, blocking- I was actually going to say also not blocking on this is okay given that the perm prompt existing will slow down the flow to this crash. So the probability of a user hitting this crash probably isn't likely.
Believed fixed by bug 837539
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: