Extension launchWebAuthFlow with Pinterest OAuth ends up crashing Chrome because of segfault
Reported by
leveille...@gmail.com,
Oct 17 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/9.1.3 Safari/601.7.8 Steps to reproduce the problem: 1. Load unpacked extension 2. This will add a StackOverflow icon to the extension toolbar, click on it to launch the extension OAuth call to Pinterest 3. Chrome will crash with a segmentation fault. What is the expected behavior? No crash What went wrong? Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000001e8 Did this work before? Yes Not sure Does this work in other browsers? N/A Chrome version: 53.0.2785.143 (64-bit) Channel: stable OS Version: OS X 10.11.6 Flash Version: n/a 1- As far as I know, this used to work. This code was used by the extension. However, the extension is used only by one person and the access token is stored in local storage so if this bug was caused by a regression, it could have happened at any point in the last few months. 2- The authURL, if copy-pasted into the browser address bar, works just fine. 3- If we change the AuthURL a slight bit, let's say to add a "test" after the last slash, there is no crash: https://api.pinterest.com/oauth/test?client_id....
,
Oct 17 2016
As part of the "enable crash report" thing, Chrome detected a new version and installed 54.0.2840.59 (64-bit). I can't reproduce anymore. So it might be that this version fixes it. I have an unpatched computer at home, I'll try the test case, upgrade and try again and let you know if the latest release fixes this problem.
,
Oct 18 2016
Tested in chrome stable #54.0.2840.59 on MAC 10.12, win 10.0 & Ubuntu 14.04 and not able to reproduce the issue.Please find the snap shot for reference. Thanks for the update.Request you to please provide the update as per your above comment#2. Thank you in advance.
,
Oct 18 2016
Hi, I was able to test it this morning and yes, the very latest update fixes this bug. That update was very timely for me! :) This ticket can be closed.
,
Oct 19 2016
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by leveille...@gmail.com
, Oct 17 2016