Issue metadata
Sign in to add a comment
|
Clash of Clans and Boom Beach not working.
Reported by
dvessel...@gmail.com,
Nov 15 2016
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8743.83.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.93 Safari/537.36 Platform: 8743.83.0 (Official Build) stable-channel cyan Steps to reproduce the problem: 1. Open either Boom Beach or Clash of Clans 2. Boom Beach will not load or allow you scout/attack 3. Clash of Clans will not allow you to scout or attack What is the expected behavior? Prior to the November update, games worked perfectly. Now both are broken and this is frustrating. Games should allow you to play. What went wrong? Games are freezing up and shutting down. Problem only occurs after the update. Tried the Beta channel but it does the same there. Unable to recover OS 53 to allow me to access content. Did this work before? Yes OS 53 Chrome version: 54.0.2840.93 Channel: stable OS Version: 8743.83.0 Flash Version: Shockwave Flash 23.0 r0 Please help me either download the prior OS until this is fixed or help me find a work around until the bug is fixed.
,
Nov 17 2016
Sorry, not skilled enough to understand your comment: Platform>ARC
,
Nov 27 2016
I'm having the exact same problem. Chrome OS Version: Version 54.0.2840.101 Platform 8743.85.0 (Official Build) stable-channel veyron_minnie ARC Version 3487238 Firmware Google_Veyron_Minnie.6588.197.0 Chromebook Model: Asus Chromebook Flip Issue description: When the Play Store was added to Chromebooks, I tested Clash of Clans on the Asus Flip. It worked so I purchased myself the Asus Flip. Forward further a few updates and Clash of Clans began crashing during certain game-play activities such as making an attack, watching replays and accessing the settings. When this issue first occurred, I used the "Power Wash and Revert" option to get the app working again. We are so many OS versions ahead now, this option no longer works for me. Any help on this would be greatly appreciated. The only reason I bought this particular Chromebook was to play the Clash of Clans game, which almost renders the device useless for me. Thanks in advance.
,
Nov 28 2016
,
Nov 28 2016
,
Nov 28 2016
Some more information might be helpful. 1. alt-shift-I lets you send a Google Feedback, if you could refer to this bug in the message and send some feedback logs after crash happens, it would be good. 2. we're nearing stable update to M-55, if you can see if beta channel (M-55) reproduces the issue that might be helpful. https://support.google.com/chromebook/answer/1086915?hl=en
,
Nov 28 2016
( there was a separate report that might or might not be related in internal b/32291573 not much more information, might be an update on the app side causing this failure )
,
Nov 29 2016
Reproduced on my samus ( feedback ID 17867058529 for reference ) Crashing with signal 11 (segmentation fault). 11-29 11:31:07.378 9939 9966 W google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ### 11-29 11:31:07.378 9939 9966 W google-breakpad: Chrome build fingerprint: 11-29 11:31:07.378 9939 9966 W google-breakpad: 8.551.24 11-29 11:31:07.378 9939 9966 W google-breakpad: 812 11-29 11:31:07.378 9939 9966 W google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ### 11-29 11:31:07.378 9939 9966 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3624 in tid 9966 (GLThread 611) 11-29 11:31:07.430 22 22 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-29 11:31:07.430 22 22 F DEBUG : Build fingerprint: 'google/samus/samus_cheets:6.0.1/R55-8872.54.0/3500695:user/release-keys' 11-29 11:31:07.431 22 22 F DEBUG : Revision: '0' 11-29 11:31:07.431 22 22 F DEBUG : ABI: 'x86' 11-29 11:31:07.431 22 22 F DEBUG : pid: 9939, tid: 9966, name: GLThread 611 >>> com.supercell.clashofclans <<< 11-29 11:31:07.431 22 22 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3624 11-29 11:31:07.439 22 22 F DEBUG : eax 00003620 ebx f723b710 ecx 00000000 edx 0000001f 11-29 11:31:07.439 22 22 F DEBUG : esi f84cfd30 edi 00000000 11-29 11:31:07.439 22 22 F DEBUG : xcs 00000023 xds 0000002b xes 0000002b xfs 0000007f xss 0000002b 11-29 11:31:07.439 22 22 F DEBUG : eip f720ba06 ebp 00000000 esp e9160df0 flags 00210286 11-29 11:31:07.442 22 22 F DEBUG : 11-29 11:31:07.442 22 22 F DEBUG : backtrace: 11-29 11:31:07.442 22 22 F DEBUG : #00 pc 00016a06 /system/lib/libandroidfw.so (_ZN7android12AssetManager24openNonAssetInPathLockedEPKcNS_5Asset10AccessModeERKNS0_10asset_pathE+22) 11-29 11:31:07.442 22 22 F DEBUG : #01 pc 00016e75 /system/lib/libandroidfw.so (_ZN7android12AssetManager4openEPKcNS_5Asset10AccessModeE+149) 11-29 11:31:07.442 22 22 F DEBUG : #02 pc 00009d4a /system/lib/libandroid.so (AAssetManager_open+58) 11-29 11:31:07.442 22 22 F DEBUG : #03 pc 002fb95d /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.442 22 22 F DEBUG : #04 pc 002fb788 /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.442 22 22 F DEBUG : #05 pc 002cae4e /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.442 22 22 F DEBUG : #06 pc 002fa8d9 /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.442 22 22 F DEBUG : #07 pc 002f751d /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.443 22 22 F DEBUG : #08 pc 002f88ea /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.443 22 22 F DEBUG : #09 pc 001d54c0 /data/app/com.supercell.clashofclans-1/lib/x86/libg.so 11-29 11:31:07.721 22 22 F DEBUG : 11-29 11:31:07.721 22 22 F DEBUG : Tombstone written to: /data/tombstones/tombstone_00 11-29 11:31:07.721 22 22 E DEBUG : AM write failed: Broken pipe 11-29 11:31:07.721 64 10028 W ActivityManager: Force finishing activity com.supercell.clashofclans/.GameApp
,
Nov 30 2016
,
Feb 26 2017
Anything yet?
,
Mar 22 2017
Clash Of Clans working now with most recent update, noted below Version 56.0.2924.110 Platform 9000.91.0 (Official Build) stable-channel veyron_minnie ARC Version 3756504 Firmware Google_Veyron_Minnie.6588.237.0
,
Apr 11 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2018
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by vsu...@chromium.org
, Nov 17 2016