Closed Bug 1328794 Opened 7 years ago Closed 7 years ago

Intermittent browser/base/content/test/webrtc/browser_devices_get_user_media_screen.js | application crashed [@ jemalloc_crash]

Categories

(Core :: WebRTC, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

Rank: 15
Priority: -- → P1
jan-ivar - can you take a look?
Flags: needinfo?(jib)
Hmm, I see interesting patterns here. First I was thinking it could be a latent bug in webrtc.org 49.

But we have bug 1324218 and bug 1324220 that occurred before the webrtc.org update, and bug 1329259 and this one occurred after. All are on OSX 10.10 opt. Do we have threading or timing issues I wonder?
See Also: → 1324218, 1324220, 1329259
alex: any thoughts given the timeframe?  There were some other Mac memory/jemalloc issues with full-duplex work.
Flags: needinfo?(achronop)
Bug 1329594 has the same crash reason (EXC_BAD_ACCESS / EXC_I386_GPFLT) and there no obvious reason why we crash at that point. Reading about EXC_I386_GPFLT I see that for 64-bit systems the addressing could be a reason (non canonical pointers). Another likely issue is unaligned SSE register which we use in our case. In general this something reported for first time, we did not have it and I do not have a clear root cause.
Flags: needinfo?(achronop)
See Also: → 1329594
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
This appears to have been fixed by something else.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jib)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.