Issue metadata
Sign in to add a comment
|
System freeze with glimmer while surfing with 16 open tabs
Reported by
nurwegen...@googlemail.com,
Mar 29 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9405.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3051.3 Safari/537.36 Platform: 9405.0.0 (Official Build) canary-channel glimmer Steps to reproduce the problem: 1. Surf with more than 10 open tabs 2. Just surf and wait for the freeze What is the expected behavior? No freeze What went wrong? Hole system freezed. I need to hold the power button for seconds to make a hard-shutdown. Before I try different key-kombinations and try to put the lid close/open. When the lid was close the display just stay on. Did this work before? Yes Today I made an update to the newest canary, before this update it runs well without freeze. Before this I had sometimes a freeze. Chrome version: 59.0.3051.3 Channel: canary OS Version: 9405.0.0 Flash Version: 25.0.0.143 /run/imageloader/PepperFlashPlayer/libpepflashplayer.so The last time the cary updates bringing more problems to my glimmer device. For about 4 weeks I had no touch input and got a lot more freezes like now. I hope you find something in my logs. Greetings by Daniel
,
Apr 19 2017
Please merge with: Issue 712692 I found a lot of crashes in chrome://crashes Absturz-ID Chrome (Server-ID: c20cb68e80000000) Absturz-ID Chrome (Server-ID: 3548631e90000000) Absturz-ID Chrome (Server-ID: 13fc2d1e90000000) Absturz-ID Chrome (Server-ID: 8dec751e90000000) Absturz-ID Chrome (Server-ID: 0904cf9230000000) Absturz-ID Chrome (Server-ID: 3a9e7b9230000000) Absturz-ID Chrome (Server-ID: 02d9f2d640000000) Absturz-ID Chrome (Server-ID: 1a61de7690000000) Absturz-ID Chrome (Server-ID: d192d67690000000) Absturz-ID Chrome (Server-ID: 4572967690000000) Absturz-ID Chrome (Server-ID: d98442fc30000000) Absturz-ID ChromeOS (Server-ID: babb4cfc30000000) Absturz-ID ChromeOS (Server-ID: 47279ad690000000) Absturz-ID ChromeOS (Server-ID: 61f5388e80000000) Absturz-ID ChromeOS (Server-ID: ccfcd1fa90000000) Absturz-ID ChromeOS (Server-ID: ec3721fa90000000) Absturz-ID ChromeOS (Server-ID: 126ecb0e80000000) Absturz-ID ChromeOS (Server-ID: 68c596fa90000000) Absturz-ID ChromeOS (Server-ID: 76c42b5640000000) Is this usefull?
,
Apr 19 2017
Thank you for providing more feedback. Adding requester "dhaddock@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2017
Looks like your crash is being seen on other devices too I will duplicate your issue into another one |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dhadd...@chromium.org
, Apr 19 2017