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

Issue 797505 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
ellyjo...@chromium.org
█ sc00335...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome crashes with EXC_BAD_ACCESS (SIGSEGV) due to KERN_INVALID_ADDRESS at 0x00000000000000d0

Reported by bcanada...@gmail.com, Dec 23 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. Create unpacked extension.
2. Have all background script code inside a immediately invoked function expression.
3. Call chrome.identity.launchWebAuthFlow() in background script.

What is the expected behavior?
Chrome crashes in Thread 0 with the error message described in the one-line summary above.

What went wrong?
See file.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.84  Channel: n/a
OS Version: OS X 10.12.6
Flash Version: 

The error only occurs sometimes, and I haven't found a way to deliberately reproduce the crash.
chrome crash error.txt
4.3 KB View Download

Comment 1 by bjthedj...@gmail.com, Dec 24 2017 

how to i fix this issue

Comment 2 by krajshree@chromium.org, Dec 25 2017

Labels: Needs-Triage-M63

Comment 3 by meh...@chromium.org, Dec 26 2017

Labels: Stability-Crash

Comment 4 by sc00335...@techmahindra.com, Dec 26 2017

Cc: sc00335...@techmahindra.com
Components: Platform>Extensions
Labels: Needs-Feedback Triaged-ET
@Reporter: Please provide sample test file to check this issue.This would help in furtehr triaging of the issue from TE end.

Thanks!

Comment 5 by ellyjo...@chromium.org, Jan 29 2018

Cc: ellyjo...@chromium.org
Owner: rsesek@chromium.org
Status: Assigned (was: Unconfirmed)
rsesek: there's a crash dump of some sort attached to this report, but I can't figure out how to use crsym to symbolize it. Can you help?

Comment 6 by rsesek@chromium.org, Jan 29 2018

Owner: ----
Status: Unconfirmed (was: Assigned)
This is missing the whole crash report. Please attach the original file instead of just the top snippet.

Comment 7 by ellyjo...@chromium.org, Mar 5 2018 

Mac triage: WontFix old issue without feedback.

Comment 8 by ellyjo...@chromium.org, Apr 9 2018

Status: WontFix (was: Unconfirmed)
►

Sign in to add a comment