crash [@ libobjc.A.dylib@0xb150][@ libobjc.A.dylib@0xb158]

RESOLVED INCOMPLETE

Status

()

Core
WebRTC: Audio/Video
--
critical
RESOLVED INCOMPLETE
4 years ago
3 years ago

People

(Reporter: bogdan_maris, Unassigned)

Tracking

({crash, stackwanted})

24 Branch
x86_64
Mac OS X
crash, stackwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

4 years ago
Steps to reproduce:
1. Open a WebRTC session with another person in Chrome and Firefox 24 beta 1 at the same time.
(http://tokbox.com/opentok/webrtc/demo)
2. After a few minutes close the session from Firefox.

Notes:
1. This issue is intermittent, I was able to crash it three times with two different signatures.

https://crash-stats.mozilla.com/report/index/758d07d6-785d-4d65-bfe4-1d8882130813
https://crash-stats.mozilla.com/report/index/e6fb6c54-313b-4aa4-a6e5-8f7c12130813
Crashing on shutdown (from the report) somewhere in Apple's code it appears.  The stack is pretty useless, likely someone needs to catch it in a debugger.

If this is only happening in the use case given (shutdown, in a call, while Chrome is also in a call) -- this is not high priority.  If we see it more general usecases, that will change things.
Keywords: crash

Updated

4 years ago
Severity: normal → critical
Crash Signature: [@ libobjc.A.dylib@0xb150] [@ libobjc.A.dylib@0xb158]
Keywords: stackwanted
Hardware: x86 → x86_64
I tried a couple of times to reproduce this in a custom (non-opt) build made from yesterday's m-c code, and failed to do so.  I tested on a Retina MBP running OS X 10.7.5.  I'll wait until this is more urgent to dig further.

Bogdan, can you reproduce with today's mozilla-central nightly?
Flags: needinfo?(bogdan.maris)
(Reporter)

Comment 3

4 years ago
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:26.0) Gecko/20100101 Firefox/26.0

I was unable to reproduce the crash on latest Nightly (buildID: 20130819030205).
Flags: needinfo?(bogdan.maris)
Steven, can you try with a 24 beta?
Bogdan, can you re-verify with the current 24 beta, and if it happens, please re-try with a 24 beta debug build? 
If possible and if it is repeatable, please try to get a stack (run under gdb, if you can, and capture the output of "where full" and "info threads").

Thanks
Flags: needinfo?(smichaud)
Flags: needinfo?(bogdan.maris)
I just tested with FF 24b3 and didn't crash.

But along the way I realized I'm not sure I'm testing "correctly".  It's not clear what "open a WebRTC session with another person" means, in the context of the test URL.

Bogdan, please provide detailed STR.
Flags: needinfo?(smichaud)
By the way, the FF beta builds (even the debug ones) have their symbols stripped.  So gdb traces made from them won't be particularly useful (all the Mozilla-specific symbols will be wrong).

Our only builds that *don't* have their symbols stripped are non-debug mozilla-central nightlies.
(Reporter)

Comment 7

4 years ago
(In reply to Randell Jesup [:jesup] from comment #4)
> Bogdan, can you re-verify with the current 24 beta, and if it happens,
> please re-try with a 24 beta debug build? 

I was able to reproduce the crash with those two signatures:
24 beta 4 build:
- https://crash-stats.mozilla.com/report/index/8560bfc3-b6a9-484f-9996-8478b2130821
- https://crash-stats.mozilla.com/report/index/6b936188-21d2-475d-8b21-d92b22130821

24 beta debug:
- https://crash-stats.mozilla.com/report/index/ad6de672-bdbf-42df-959a-6f19a2130821
- https://crash-stats.mozilla.com/report/index/4501beed-83f3-4939-bb7e-dda462130821 - This is a new signature that I did not encountered earlier.

I was following Firefox process in Activity monitor and I noticed a memory increase until about 1.9GB (there is when I closed the tab with the WebRTC) and CPU Usage 100%.

> If possible and if it is repeatable, please try to get a stack (run under
> gdb, if you can, and capture the output of "where full" and "info threads").
> 
> Thanks

Based on Stevens comment should I run beta under gdb and try to reproduce the crashes or on Nightlys?

(In reply to Steven Michaud from comment #5)
> I just tested with FF 24b3 and didn't crash.
> 
> But along the way I realized I'm not sure I'm testing "correctly".  It's not
> clear what "open a WebRTC session with another person" means, in the context
> of the test URL.
> 
> Bogdan, please provide detailed STR.

STR:
1. On Mac OS X 10.7 open Firefox and go to http://tokbox.com/opentok/webrtc/demo
2. Open www.stirileprotv.ro in another tab (it`s a website with lots of content, it somehow helps).
3. Copy the link from "Share this URL:" from the bottom of the page.
4. Open that link on another machine on the same Firefox version. (the browser that is opened might not be important but its the way I reproduced it).
5. On Mac open Chrome and go to http://tokbox.com/opentok/webrtc/demo
6. Copy the link from "Share this URL:" from the bottom of the page.
7. Open that link on another machine (I used a third machine) on Chrome.
8. Focus Firefox opened on step 1, switch between tabs, go to the tab where stirileprotv is opened and give a few scrolls.

Notes:
1. All machines should and must have webcams.
2. It may not work all the time using this steps.
Flags: needinfo?(bogdan.maris)
I only have two machines with webcams.  But I tried your STR with them (both running OS X 10.7.5 and FF 24b4), and still can't reproduce any crashes.

Both of my machines are MacBook Pros -- one a Retina, and the other not.

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.