Frequent aw snaps screen at any page on application
Reported by
kirtesh....@gmail.com,
Jun 14 2016
|
||||
Issue description
Chrome Version : 51.0.2704.84
URLs (if applicable) :
Other browsers tested: Not tested as our application best works on chrome
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: No
Firefox: No
IE: No
What steps will reproduce the problem?
(1) Frequent aw snaps screen at any page on application
(2)
(3)
What is the expected result? No aw snap screen should be shown
What happens instead?
Please provide any additional information below. Attach a screenshot if
possible.
,
Jun 15 2016
I should have mentioned: OS: Debian sid (4.6.1-1) Chromium: Version 51.0.2704.79 built on Debian stretch/sid, running on Debian stretch/sid Also, my Gmail page works fine on this machine using Firefox ESR 45.2.0 and other Windows 10 machines using latest Google Chrome.
,
Jun 15 2016
Unable to reproduce the issue on windows 7, Linux Ubuntu 14.04 using chrome version 51.0.2704.84 and canary 53.0.2767.0.Not observed any error while browsing. Request you once please try the issue on new profile and if the issue still persists please provide us the crash id from chrome://crashes . Thanks,
,
Jul 14 2016
@mackeul -- Could you please verify on Chrome Stable# 51.0.2704.106 and Chrome Canary# 54.0.2794.0 and respond to comment# 3. Thanks in Advance.
,
Jul 24 2016
Debian still only has version 51.0.2704.79-1 available through apt. I've no idea what canary is, I've never used it, at least not directly. Tried creating new profile (moved .config/chromium to chromium.old)... still same result when going to Gmail ... chrome://crashes gives me: Crashes Crash reporting is disabled. Crash reporting is not available in Chromium.
,
Aug 9 2016
,
Aug 9 2017
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 |
||||
Comment 1 by mack...@gmail.com
, Jun 15 2016