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

Issue 641031 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Sep 2017
Cc:
█ brajkumar@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

crash

Reported by rcheng...@student.glendale.edu, Aug 25 2016 
Chrome Version: 52.0.2743.116
Operating System: e.g., "Windows 7", "Mac OSX 10.6"

URL (if applicable) where the problem occurred:

Can you reproduce this problem?

What steps will reproduce this problem? (or if it's not reproducible, what were you doing just before the problem)?

1. chrome crashed

*Please note that issues filed with no information filled in above will be marked as WontFix*

****DO NOT CHANGE BELOW THIS LINE****
report_id:0d18bd0600000000

Comment 1 by brajkumar@chromium.org, Aug 26 2016

Cc: brajkumar@chromium.org
Components: Blink>WebRTC
Labels: Stability-Crash Needs-Feedback
rcheng@ - Are you able to repro this crash consistently? If yes, please provide the manual steps to repro it. 

Unable to fetch the stack trace information from the provided crash ID from crash server. It will be better if you could provide few more crash ID's for further investigation.

Thanks!

Comment 2 by jansson@chromium.org, Sep 1 2016

Components: -Blink>WebRTC
[triage] not related to WebRTC. The chrome version with webrtc in it's name is nothing we know about.
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 4 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment