Issue metadata
Sign in to add a comment
|
Chromium crashes when logging into gmail
Reported by
redso...@gmail.com,
Dec 7 2016
|
||||||||||||||||||||
Issue description
Chrome Version : 55.0.2883.75
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: OK
Firefox: OK
IE: OK
Chrome: OK
What steps will reproduce the problem?
I am using Debian sid and chromium installed from the official debian repositories.
The version from chrome://help is 55.0.2883.75
The browser tabs keep on crashing when viewing gmail.
I have tried clearing my cache and cookies.
I have tried with incognito mode and the issue is still there.
I have tried with hardware acceleration enabled and disabled and the issue is still there.
I have tried to reset my chrome settings and the issue is still there.
I can't try canary because it's not available for linux.
I don't know if it is relevant, I am using the nouveau nvidia drivers (inside linux kernel).
I also have no other plugins than Chromium PDF Viewer.
The only workaround for me is to downgrade the browser to version 53.0.2785.92 that I happened to have in the /var/cache/apt/archives/
However I would really prefer having the latest version due to security and other reasons.
What should I do?
,
Dec 8 2016
redsolja@ Thanks for filing this issue, Are you able to reproduce this crash consistently and is it observed on incognito mode? If yes, could you please provide sample crash Id's from chrome://crashes for further investigation. Thanks!
,
Dec 8 2016
Yes the browser crashes in incognito mode as well. I say that at the description. I am attaching the gdb crash report and the ldd output
,
Dec 8 2016
There is no crash ID's got generated under chrome://crashes?
,
Dec 8 2016
No chrome://crashes sais that crash reporting is disabled. I followed the steps shown here https://goo.gl/uWqw1X
,
Dec 8 2016
OK I think I understand now. Should I enable the automatic crash submission in order to view the chrome://crashes? Is it still needed, should I still do it or are the attached data enough for you?
,
Dec 8 2016
It would be better if you enable the automatic crash submission and provide few sample crash Id's
,
Dec 8 2016
chrome://crashes still displays the same message "Crash reporting is disabled", regardless of the automatic crash submission setting that I enabled. I am attaching a crash screen.
,
Dec 8 2016
This is a debian chromium build. Chromium builds don't have crash reporting because Google didn't build the software so we don't have the debug symbols for the release that was build. So you need to consult the debian debug symbols; see here: https://wiki.debian.org/Chromium/Debugging Hopefully you can provide us the symbolized stack traces using that method.
,
Dec 14 2016
,
Dec 21 2016
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
,
Jan 13 2017
If any latest update available on this issue please update the bug with latest behavior. As per comment #9 removing myself from owners list.
,
Jan 25 2017
,
Jan 25 2017
redsolja-- Could you please reply to comment #9 and update the thread . Thanks!
,
Jan 25 2017
Hello, sorry for the late feedback. The bug is not valid now, it does not happen at the latest version. I guess this can be marked as resolved.
,
Jan 25 2017
Thanks redsolja@ for the update. Marking the issue status as Won't Fix as per comment #15. Please feel to free to log a new defect once you face the issue again. Thank You. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Dec 8 2016