New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 624433 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Browser tab crashes with Aw snap on Blackboard Session

Reported by abhina...@gmail.com, Jun 29 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Load URL - https://apollodemo01.bbcollab.com/collab/ui/session/guest/8A5D356DFE1118DC9196240915B8CD23
2. Enter name and join.
3. Start microphone, camera (look for mic and cam icons on the bottom of the screen). 
4. Click on My Settings button (to the left of microphone icon at the bottom of the screen), then click on Generate Number available under Use your phone for audio.
5. Use Phone (or Skype) to call US number 571-392-7654.
6. Enter PIN followed by # as prompted.
7. Click on the Share Content (+ icon on the top right). Under Interact, Click on Breakout Groups.
8. Drag user from Main Room to Group 1, then click on the Start button at the bottom right of the screen.

What is the expected behavior?
Breakout Group should have started.

What went wrong?
The browser tab crashes with Aw, Snap!

Did this work before? Yes Chrome 50

Chrome version: 51.0.2704.106  Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 22.0 r0

Two crash reports have been filed w.r.t. Blackboard Session - https://bugs.chromium.org/p/chromium/issues/detail?id=619920 and https://bugs.chromium.org/p/chromium/issues/detail?id=623076
 
Cc: brajkumar@chromium.org
Labels: Needs-Feedback crash
abhinajao@ - Thanks for filing this issue, Could you please provide any sample crash ID's from chrome://crashes which is related to this issue. It will be helpful to triage further.

Thanks!
Labels: -crash Stability-Crash

Comment 3 by abhina...@gmail.com, Jun 30 2016

Thanks for the follow-up brajkumar, here are some recent crash IDs:
- Crash ID e169039600000000 (8cbc3641-7a44-4ed4-b563-d18ea2cfb500)
- Crash ID fa1a672600000000 (630a5b55-e9c5-4aff-bdd1-c9f432624206)
- Crash ID 3177222600000000 (3df10ad2-826e-4e6a-8e48-73698274128b)
- Crash ID 21f2ede600000000 (bec9a27c-4169-4dc1-adc5-0a6874d99ee9)
- Crash ID 630071bc00000000 (42d15f3b-b8a9-4aa4-bc19-5fd84800ecbb)
- Crash ID 38ef79e600000000 (c20c7932-da45-4b9f-a8a9-7dd9f9768ffd)
- Crash ID d19c97fa00000000 (0eecfc1a-0d6e-4fad-8b3b-e2bb1b38fb12)
 
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 30 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-TestConfirmation
Wow, these are almost all different crashes.

Could it be that something is going very wrong in this process (e.g, causing an OOM), which is then exploding in different places later?

Adding Needs-TestConfirmation to get manual qa to repro

- Crash ID e169039600000000 (8cbc3641-7a44-4ed4-b563-d18ea2cfb500)
  https://crash.corp.google.com/browse?stbtiq=e169039600000000
  WTF::String ctor in autofill (oom?)

- Crash ID fa1a672600000000 (630a5b55-e9c5-4aff-bdd1-c9f432624206)
  https://crash.corp.google.com/browse?stbtiq=fa1a672600000000
  issue 592779 (not diagnosed, but maybe oom?)

- Crash ID 3177222600000000 (3df10ad2-826e-4e6a-8e48-73698274128b)
  https://crash.corp.google.com/browse?stbtiq=3177222600000000
  cricket::TransportChannelImpl dtor

- Crash ID 21f2ede600000000 (bec9a27c-4169-4dc1-adc5-0a6874d99ee9)
  https://crash.corp.google.com/browse?stbtiq=21f2ede600000000#0
  oom killer

- Crash ID 630071bc00000000 (42d15f3b-b8a9-4aa4-bc19-5fd84800ecbb)
  https://crash.corp.google.com/browse?stbtiq=630071bc00000000#0
  cricket::BaseChannel::set_rtcp_tarnsport_channel

- Crash ID 38ef79e600000000 (c20c7932-da45-4b9f-a8a9-7dd9f9768ffd)
  https://crash.corp.google.com/browse?stbtiq=38ef79e600000000#0
  issue 592779 again

- Crash ID d19c97fa00000000 (0eecfc1a-0d6e-4fad-8b3b-e2bb1b38fb12)
  https://crash.corp.google.com/browse?stbtiq=d19c97fa00000000#0
  webrtc::RTPReceiverVideo dtor
Labels: TE-NeedsTriageFromMTV
Owner: ----
Requesting someone from MTV team to look in to this issue for further triaging.
Labels: Needs-Feedback
Unable to reproduce the issue on Mac OSX 10.11.5 - Version 52.0.2743.82 (64-bit)

abhinajao@, can you please upgrade to the latest stable build available and check if you still see this issue ?
Screen Shot 2016-07-25 at 4.29.26 PM.png
112 KB View Download

Comment 8 by abhina...@gmail.com, Jul 27 2016

Thanks team. I was able to verify that Browser tab crash issue is fixed on Version 52.0.2743.82 (64-bit) on my MacBook OS X 10.11.6
Project Member

Comment 9 by sheriffbot@chromium.org, Aug 5 2016

Labels: -Needs-Feedback Needs-Review
Owner: pucchakayala@chromium.org
Thank you for providing more feedback. Adding requester "pucchakayala@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Closing, as per c#8.

Sign in to add a comment