Lots of Aw snaps in the latest Chrome build |
||||||||||||||||
Issue descriptionLots of Aw snaps in the latest Chrome build .144 for M53 8530.93.0 Beta for Cave and M53 Stable for all boards. Feedback reports can be found here.https://feedback.corp.google.com/product/208/neutron?lView=rl&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=Aw%20snap The issue repros on multiple boards. Can you please take a look and
Showing comments 5 - 104
of 104
Older ›
,
Oct 1 2016
Quickly check the Feedbacks info, most of bugs are reported for chrome 53.0.2785.103 or older build(M49..). Will try to reproduce the crash sites on the latest M53~M55.
,
Oct 6 2016
Please find the crash ID's below: Crash ID ChromeOS_ARC (Server ID: ebca499900000000) Crash ID ChromeOS_ARC (Server ID: 7021ee1d00000000)
,
Oct 6 2016
All 25 of my open tabs Aw-Snap'd one after the other. I wasn't fast enough to grab a screenshot of the task manager but I saw the Browser process jump to 90% when the tabs began to crash then down to about ~8% after all tabs had crashed. ChromeOS - 53.0.2785.144/8530.93.0
,
Oct 6 2016
I was editing a google spreadsheet when I observed the crash of all 25 tabs.
,
Oct 6 2016
HUh so we see it in the latest stable too. It is a bit late to get this fixed in M53 since our last stable is now close to being pushed. Let us aim to get this fixed before M54 hits stable on the 17th of october. Geetha, do you repro this on M54 latest build too? dianders@ who should look at this particular crash?
,
Oct 6 2016
,
Oct 11 2016
Issue 648956 has been merged into this issue.
,
Oct 12 2016
I'm massively behind on email right now and in the middle of several Kevin fires, so maybe not best for me to triage. Sameer (the overall kernel lead for Chrome OS) is probably a better candidate. Adding Dylan too since at least two of the bugs above: Crash ID ChromeOS_ARC (Server ID: ebca499900000000) Crash ID ChromeOS_ARC (Server ID: 7021ee1d00000000) ...are ARC related. I don't know if all of them are.
,
Oct 15 2016
I continue to hit many aw snaps - very bad experience. In the latest occurrence, the Browser process hit 57% cpu usage. Still on: Version 53.0.2785.144 beta (64-bit) Platform 8530.93.0 (Official Build) beta-channel
,
Oct 15 2016
Patricia, Can you try to update to the Stable channel for M53 and check out the latest .96 build to see if you still experience these aw snaps?
,
Oct 16 2016
We are seeing a few reports on CBC that may be caused by this bug. We have spent quite a lot of effort chasing other causes. #CBC-RS/TC-watchlist https://productforums.google.com/forum/#!topic/chromebook-central/xOdN9o9a7ig https://productforums.google.com/forum/#!topic/chromebook-central/K5hy3S0FJQU https://productforums.google.com/forum/#!topic/chromebook-central/wCqpVaYj-T8 https://productforums.google.com/forum/#!topic/chromebook-central/e2MAzw-AgMs https://productforums.google.com/forum/#!topic/chromebook-central/dUASipYQcOQ https://productforums.google.com/forum/#!topic/chromebook-central/wM1ENBsaCeo
,
Oct 16 2016
Feedback sent this morning at 8:11am EDT About 10 tabs aw snapped at the same time Version 53.0.2785.154 (64-bit) Platform 8530.96.0 (Official Build) stable-channel auron_yuna Firmware Google_Auron_yuna.6301.59.8
,
Oct 17 2016
I have been having many issues with my chromebook coming up with Aw snap pages. Following advice I have closed down my chromebook all the way each night, limited my tabs to no more than 3, powerwashed by chromebook three times, reset my settings. Still happening. I also pushed control alt t and ran a memory_test which went to done with all ok's. another issue that is happening is that when I am in google docs I cannot get the curser to the correct position to start highlighting. It keeps going back to the original position. I have used google docs for years so I do know how to do it, but suddenly it's driving me so crazy. thanks for any help you can give.
,
Oct 25 2016
Hit it again, Browser process jumped to 59% and I saw 8 tabs Aw Snap. I am still on beta on this specific machine.
,
Oct 26 2016
,
Oct 26 2016
Any sign of this in 54?
,
Oct 26 2016
As per #21 Patricia machine was on Beta which is M54
,
Oct 26 2016
Actually, I am in the M53 beta dogfooding pool.
,
Oct 26 2016
Sorry didnt go thro bug thoroughly but there are few reports on M54 dupe bug Issue 639493
,
Nov 2 2016
There are also reports on Beta M54 for multiple platforms. Via a quick scanning, I see yuna, minnie, daisy.
,
Nov 2 2016
This bug will probably need to get split into multiple sub bugs since some of the issues are ARC++ related but others are from platforms where ARC++ isn't enabled yet. Lets track ARC++ related issues in this bug since the two crash IDs identified are ARC++ related: Crash ID ChromeOS_ARC (Server ID: ebca499900000000) Crash ID ChromeOS_ARC (Server ID: 7021ee1d00000000) Hopefully Elijah can triage the two crashes above. Patricia, could you send us the crash IDs from chrome://crash or your client_id and we can try to look up crashes from your system?
,
Nov 2 2016
Some of the massive "Aw, Snap..." issues right after Chrome's launch and in case when even Settings page does "Aw, Snap...", were solved by updating USB 3.x drivers. Also, not sure, but if user experiences the same issue while he has no any USB 3.x ports, then he should check MB ROM update and chipset drivers. Some useful info here: https://productforums.google.com/forum/?utm_medium=email&utm_source=ba_badge_notification#!msg/chrome/QgFp-GNoMsI/mngG71eTCAAJ
,
Nov 2 2016
The most recent crash listed is from Oct 10th but I've seen more recent tab crashes. Oct 10: Crash ID Chrome (Server ID: 37a96e4b00000000) Oct 4: Crash ID Chrome (Server ID: d987fb0b00000000)
,
Nov 2 2016
I have at least 10 crashed a day, mostly on my chrome book, but yesterday, also on my apple desktop computer!
,
Nov 2 2016
To be clear, my observed crashes were on a non-ARC++ build.
,
Nov 2 2016
Patricia, I took a look at crashes from the client ID associated with your crashes. There were 5 crashes. I have opened issue 32607304 for one of the crashes (SetWiFiTransmitPower::SetPowerMode) The other crashes are beyond my areas of expertise. Maybe abodenha can triage those? https://crash.corp.google.com/browse?q=ClientID%3D%2750044b99b90a4e07b2a74addb36f48c7%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0
,
Nov 2 2016
For SetWiFiTransmitPower::SetPowerMode, see also http://crosbug.com/p/59242
,
Nov 2 2016
#35: I think that snanda@ was just mentioning that he filed a new bug for an unrelated set_wifi_transmit_power crash reported by the same client. That's unlikely to have anything to do with the renderer crashes reported here.
,
Nov 2 2016
The ChromeOS_ARC issues are benign log messages (tracked in b/28520469) and shouldn't be causing browser crashes. I'm going to investigate having these not show up in chrome://crashes because they cause a lot of false positives for other crashes. They are still situations we want to report to the crash server because they indicate an unplanned program state. Back to snanda@ who seems to be still investigating this. Let me know if there's anything else you need looked at on my end.
,
Nov 2 2016
Having snanda@ stuck with a renderer crash bug seems odd. Taking this on me for the moment until I can find a better owner. bug 594764 is making it difficult to get a handle on crashes at the moment.
,
Nov 2 2016
Seeing Aw, snaps on today's M55 beta. Feedback report: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:sahitidtest1@gmail.com&lReport=15119419081
,
Nov 3 2016
,
Nov 3 2016
glevin@ can you get in touch with patricia@ and see if you can gather more info on what's happening here? Please shelve your other work for a bit to focus on this.
,
Nov 29 2016
What's the status of the bug? My Chromebook has become unusable over the past ~month due to all the out of memory "Aw Snap" crashes. It always pegs the CPU and then the memory races upward, then multiple tabs crash. This happens regardless of whether I have no extensions enabled, am in incognito, etc. It also happens on many, many different web pages. So it's not an extension issue. And until the past month or two, I had no problems at all like this. May have started around the same time ARC was enabled?? I've done multiple powerwashes, and moved to dev channel, all to no avail. If it matters, I have an Asus C100P, but I suspect this is occurring across architectures. From what I've gathered from online forums, loads of Chromebook users are having dozens of Aw Snap crashes a day in the past month or two. If there's a chance that they're all stemming from one bug, it should be super high priority. I'm about to toss my Chromebook forever and go back to a (stock) Linux distro, it's simply unusable like this.
,
Nov 29 2016
OK, I have some information that could be useful. I had not yet tried working in guest mode when I posted the last comment (Comment 42). I've now tried guest mode over the past half-day and the multiple tab crashing issue seems to have resolved. I had a one tab crash, but it was a JS-heavy site that occasionally crashed before this issue, and importantly the crash was limited to that single tab. This is back on the stable channel. Not sure why guest mode would be different from the other mode with all the extensions disabled (unchecked), or working with just an incognito mode browser open, but it appears to have resolved the issue. Maybe this will help someone triaging? I did notice that Google Play is not available in guest mode. Unfortunately, guest mode is not a workable solution for me since I can't install the Secure Shell extension I need for work. But at least I can browse the web now.
,
Dec 6 2016
I've been looking at this for weeks, and haven't been able to find any smoking gun(s). Of the four crash reports mentioned above, there are: * Two identical ones from the android (ARC++) stack, inside com.android.server.am.ActiveServices.serviceDoneExecutingLocked() * One during shutdown (inside content::BrowserMainLoop::ShutdownThreadsAndCleanUp()) * One during ChromeBrowserMainParts message loop, specifically 6 levels down in ash::LockStateController::OnLockFailTimeout() Additionally, crash id 778276c300000000 from patricia@ has this stack: (chrome -unix_domain_socket_linux.cc:127 ) base::UnixDomainSocket::RecvMsgWithFlags (chrome -broker_host.cc:182 ) sandbox::syscall_broker::BrokerHost::HandleRequest (chrome -broker_process.cc:90 ) sandbox::syscall_broker::BrokerProcess::Init (chrome -bpf_gpu_policy_linux.cc:382 ) content::GpuProcessPolicy::InitGpuBrokerProcess (chrome -bpf_gpu_policy_linux.cc:296 ) content::GpuProcessPolicy::PreSandboxHook (chrome -sandbox_seccomp_bpf_linux.cc:200 ) content::SandboxSeccompBPF::StartSandbox (chrome -sandbox_linux.cc:281 ) content::LinuxSandbox::StartSeccompBPF (chrome -sandbox_linux.cc:359 ) content::LinuxSandbox::InitializeSandboxImpl (chrome -gpu_main.cc:320 ) ContentSandboxHelper::EnsureSandboxInitialized (chrome -gpu_init.cc:232 ) gpu::GpuInit::InitializeAndStartSandbox (chrome -gpu_main.cc:250 ) content::GpuMain (chrome -content_main_runner.cc:779 ) content::ContentMainRunnerImpl::Run (chrome -content_main.cc:20 ) content::ContentMain I see no common threads here. I've looked through 10 recent system_logs.txt from https://feedback.corp.google.com/product/208/neutron?lView=rl&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=aw%20snap%20AND%20tag:%23label%3EBetaChannel and saw no common problems. They seemed to fall into two general categories: * veyron_minnie devices (6), where logs contained no indication of Tab problems * other devices (peppy (2), gnawty, samus), where logs contained some variant of WARNING:sad_tab.cc(205)] Tab Killed: <URL: 20> WARNING:oom_memory_details.cc(46)] Tab OOM-Killed Memory details: <URL: 16> (1093 ms): <dump follows> The number of these entries varied from 1 to 20 per device. Here's the first such entry from a device with two sad tabs: [745:745:1107/141146:WARNING:oom_memory_details.cc(46)] Tab OOM-Killed Memory details: <URL: 7> (207 ms): Browser 124 MB private, 125 MB shared, 87 MB swapped Extension [Adblock Plus] 109 MB private, 112 MB shared, 104 MB swapped Tab [New Tab] 75 MB private, 79 MB shared, 72 MB swapped Extension [Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB|Chrome OS XKB] 57 MB private, 60 MB shared, 49 MB swapped Extension [Hotword triggering|Google Docs Offline] 52 MB private, 55 MB shared, 50 MB swapped Background App [<URL: 3>] 45 MB private, 48 MB shared, 43 MB swapped Extension [Google+ Photos] 44 MB private, 48 MB shared, 43 MB swapped GPU [] 41 MB private, 41 MB shared, 30 MB swapped Tab (Chrome) [<URL: 4>] 28 MB private, 31 MB shared, 27 MB swapped Native Client module [<URL: 5>] 24 MB private, 24 MB shared, 24 MB swapped Zygote 21 MB private, 23 MB shared, 21 MB swapped Graphics 74.1 MB I didn't see any patterns across these logs that indicated a common problem; the items common to multiple logs looked more like log spam than causes of tab crashes. The following log entries were common across most or all of the minnie devices, but are probably unrelated; I include them only because the looked slightly less innocuous than other common errors. WARNING:tab_manager_delegate_chromeos.cc(90)] Set OOM score error: Failed to open procfs entry of process 16869 WARNING:tab_manager_delegate_chromeos.cc(90)] Set OOM score error: Write 300 to /proc/9829/oom_score_adj failed: Invalid argument ERROR:arc_net_host_impl.cc(61)] NOTREACHED() hit. (in GetStringFromOncDictionary()) ERROR:network_metrics_provider.cc(244)] NOTREACHED() hit. (in NetworkMetricsProvider::WriteWifiAccessPointProto()) At this point, I'm out of ideas on how to proceed. I do have system_logs.txt files from all 10 devices I looked at, if anyone wants to take another look.
,
Dec 10 2016
Just a copy-paste below from this debian bug tracking report if of any use. a ffmpeg flag seems to be involved. Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846648 Best, Ara From: Riku Voipio <riku.voipio@iki.fi> To: Robert Lange <rlange@corusa.net>, 846648@bugs.debian.org Subject: Re: [Pkg-chromium-maint] Bug#846648: another data point Date: Fri, 9 Dec 2016 14:42:10 +0000 On Tue, Dec 06, 2016 at 04:02:00PM -0500, Robert Lange wrote: > Debian stretch with chromium 55.0.2883.75-1 (and only chromium) pulled > in from unstable. With a brand new profile (i.e., by deleting > .cache/chromium and .config/chromium and starting Chromium) Chromium > aw-snaps on gfycat.com with very high probability. I occasionally also > see gmail aw-snap, but it's not consistent. When an aw-snap occurs, it > does not seem to affect other tabs. I managed to reproduce this. I tested a build with using embedded libraries of chromium, and the aw snap problem is gone. unbundling libraries found the library that made the difference is ffmpeg. Dropping the FF_API_CONVERGENCE_DURATION definition makes chromium work fine with system ffmpeg again, gfycat.com, gmail and www.maap.it no longer "aw, snap". The gpu stacktraces people have passed in the bug might be another bug. --- a/media/ffmpeg/ffmpeg_common.h +++ b/media/ffmpeg/ffmpeg_common.h @@ -25,14 +25,14 @@ // Disable deprecated features which result in spammy compile warnings. This // list of defines must mirror those in the 'defines' section of FFmpeg's // BUILD.gn file or the headers below will generate different structures! -#define FF_API_CONVERGENCE_DURATION 0 +// #define FF_API_CONVERGENCE_DURATION 0 > > Stack trace: > > libpng warning: iCCP: known incorrect sRGB profile > Received signal 11 SEGV_MAPERR fffffffd503afed7 > #0 0x55f8a1a8d77e <unknown> > #1 0x55f8a1a8db39 <unknown> > #2 0x7fca07207100 <unknown> > #3 0x55f8a025af21 <unknown> > #4 0x55f8a0260ffa <unknown> > #5 0x55f8a02610bb <unknown> > #6 0x55f8a5c0f612 <unknown> > #7 0x55f8a12cf952 <unknown> > #8 0x55f8a1ae7495 <unknown> > #9 0x55f8a1b13c21 <unknown> > #10 0x55f8a1aae629 <unknown> > #11 0x55f8a1aafd9d <unknown> > #12 0x55f8a1ab0240 <unknown> > #13 0x55f8a1ab0e99 <unknown> > #14 0x55f8a1ace66a <unknown> > #15 0x55f8a1aeb296 <unknown> > #16 0x55f8a1ae7322 <unknown> > #17 0x7fca071fd464 start_thread > #18 0x7fc9fc6229df clone > r8: 0000000000000000 r9: fffffffd503afecf r10: ffffe9c46ecdadef r11: > 0011bb10e749bd95 > r12: ffffffff00000000 r13: 00007fc9e5cb9548 r14: 00007fc9e5cb9540 r15: > ffffe9c46ecdadef > di: 000016393e5b0f70 si: 0000000000000013 bp: 0000000000000006 bx: > fffffffd503afecf > dx: fffffffd503afecf ax: fffffffd503afecf cx: 000016393ef75fa0 sp: > 00007fc9e5cb94a0 > ip: 000055f8a025af21 efl: 0000000000010286 cgf: 002b000000000033 erf: > 0000000000000005 > trp: 000000000000000e msk: 0000000000000000 cr2: fffffffd503afed7 > [end of stack trace] > > _______________________________________________ > Pkg-chromium-maint mailing list > Pkg-chromium-maint@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-chromium-maint
,
Dec 29 2016
I believe I may be having this issue and read in a help forum to post in this issue. I receive the "aw snap" page with several or only one tab open, have powerwashed, reset, restarted, cleared extensions, done a crosh memory test, and everything else I can find to fix this issue. Any suggestions or recent finding regarding this bug?
,
Jan 8 2017
I have been having the same problems as described by Comment 20: repeated "As, Snap" page crashes, and the cursor dislocation problem in Google Docs. I have deleted extensions, cleared cache, powerwashed. I reset my wifi router, in case that was a problem. I have an Asus C100PA-RBRKTO3 ROCKCHIP, purchased on Aug. 12, 2016. These problems seem to be getting worse, and although I like the chromebook I am getting close to giving up on it. It's disturbing that nobody seems to have a solution. Any comments?
,
Jan 13 2017
We're seeing tons of aw, snap's on latest stable build of Chrome on our Macs. Very frustrating to our staff.
,
Jan 13 2017
Re comment#48 This bug is about Chrome OS. Could you please file a new issue for what you're seeing and include the contents of chrome://crashes and chrome://version? Thank you.
,
Jan 13 2017
Since we've seen it on Macs and PCs, I thought maybe it was all the same issue? In any case, there is another issue https://bugs.chromium.org/p/chromium/issues/detail?id=673750
,
Feb 5 2017
I have been having the same problems as described above since the update (sorry don't know version) which added Google Play to my Asus Chromebook C100PA. I have sent regular feedback with 90% of the. However, it's not just confined to my Chromebook but also all the other equipment in the household ranging from Android phones and tablets, laptops running Windows and an I-Pad. On my Asus Chromebook it happens when you left click the touch-pad and the cursor moves around several times, locks the screen and then crashes the tab. On the other machines it's random from just trying to open Chrome right through to just scrolling and everything in-between. I have tried all the suggestions from deleting extensions, clearing cache, resetting chrome, power-washing, deleting chrome etc etc. I have even reset my wifi routers as well. Across all the machines in the house it is bad but particularly so on the ASUS flip. I came across this thread via the Google Chrome Support pages today having been given unhelpful for some time on there which was unnecessary given this has clearly been an issue for some time and I was surprised they didn't seem to know. Surely there must be something that can be done as sometimes it makes the machines completely unusable.
,
Feb 10 2017
Experiencing similar issue on M56 Feedback report here: https://feedback.corp.google.com/#/Report/52998588356 glevin@/abodenha@, anything relevant there?
,
Feb 13 2017
Honestly, this bug is too broad to be at all actionable. There will always be some level of "aw, snap"s. We've fixed a number of issues with memory management and several crash bugs in the last few milestones. bccheng@ does josafat@'s report look like any of the issues your team is currently looking into?
,
Feb 14 2017
Re Comment #53 on issue 651989 by abodenha@chromium.org: <abodenha@chromium.org> I am the writer of Comment #47 on this issue. Your statement that "There will always be some level of 'aw, snap"s.'" suggests that you think this is a trivial issue. On the contrary, the various problems I and others are encountering make Chrome OS unusable at this time. Therefore marketing it to the public via Chromebooks seems unethical. I enjoyed using my Asus C100-PA until the problems started cropping up. Coming across this thread, I'd been hoping that a fix was in the works. Now I plan to demand that my retailer refund my purchase cost.
,
Feb 14 2017
I couldn't agree more. I have the same model chrome book (Asus c100p) and the same usability issue. I am plagued aw snaps no matter what I do from Web surfing to simple document editing. the latest Chrome build is
,
Feb 14 2017
@54 / @55: I don't think you understand the above comment. I believe that what comment 53 means is that having a single massive bug that tries to encompass every instance of "Aw Snap" isn't helping.
Said another way: imagine if you had a single "bug tracker" entry that said "my computer sometimes crashes" and you tried to talk about every single thing in the world that could cause any computer in the world to crash. Some people would be talking about problems with their electricity (maybe their 110V outlet sometimes produces only 90V). Some people would be talking about bad RAM. Some people would be talking about bad drivers that they installed. Some about malware. ...etc, etc. Having a single discussion about "my computer crashes" doesn't help except provide people a place to vent.
Presumably the people on this thread are (mostly) talking about issues unrelated to each other, since "Aw snap" translates roughly into: "chrome crashed for some reason".
If you are having problems with your Chromebook, the absolute best things to do are:
* File feedback each time the problems happens (Shift-Alt-i)
* If possible, provide details like:
- Go to "chrome://crashes" and upload your crashes (assuming you opted into this).
If you want, you can copy crash IDs to your feedback to help link the feedback to the crashes.
- Talk about exactly what you did when you crashed and describe what happened between the crash
and filing feedback. Like:
-> Device crashed and made me log in. I logged in and immediately filed feedback.
-> I came back and opened the lid and found myself at the login screen. I filed this feedback.
-> Device screen was black for 60 seconds. I waited. It rebooted. I filed this feedback.
- If your device is frozen, use Alt-TopRowVolumeUp-R to reboot, which preserves as much logging as possible.
(there are tricks with Alt-TopRowVolumeUp-X that can give even more data, but it gets complicated).
Note that the Chrome team also pays attention to Crash Reports (assuming you opted into sending them) and tries to solve crashes that show up and are affecting lots of users. It is impossible to eliminate every source of crashes, but the team does work hard to solve them.
,
Feb 14 2017
Excellent clarification dianders@. Thank you. That's exactly what I meant. I'd like to close this out and split it into multiple other more specific issues that are easier to investigate and make progress on. Those of you who are experiencing aw, snaps can you take a look at chrome://crashes and copy/paste the contents here?
,
Feb 15 2017
Ben, any information from my feedback report that could help filing a more specific bug for this?
,
Feb 15 2017
In the feedback @52 the low-memory condition was never raised and the kernel resorts to OOM killer to free memory. cylee@'s fix is merged to 9000.84.0, so let's see if similar problems still occur after that.
,
Feb 15 2017
Here are my chrome crashes: Crashes (50) Crash ID Chrome (Server ID: f5f3113580000000) Automatically reported Wednesday, 15 February 2017 at 08:30:01 Provide additional details. Crash ID Chrome (Server ID: 32649c3580000000) Automatically reported Monday, 13 February 2017 at 18:34:27 Provide additional details. Crash ID Chrome (Server ID: a01dee5040000000) Automatically reported Monday, 13 February 2017 at 17:12:30 Provide additional details. Crash ID Chrome (Server ID: 1d1cbe4f80000000) Automatically reported Saturday, 11 February 2017 at 08:18:00 Provide additional details. Crash ID Chrome (Server ID: 8cc7ee4f80000000) Automatically reported Saturday, 11 February 2017 at 08:14:24 Provide additional details. Crash ID Chrome (Server ID: 95af0cc280000000) Automatically reported Friday, 10 February 2017 at 17:26:45 Provide additional details. Crash ID Chrome (Server ID: a743ead580000000) Automatically reported Thursday, 9 February 2017 at 09:22:55 Provide additional details. Crash ID Chrome (Server ID: 0668e2bc80000000) Automatically reported Thursday, 9 February 2017 at 09:15:38 Provide additional details. Crash ID Chrome (Server ID: d02f0e5c80000000) Automatically reported Wednesday, 8 February 2017 at 19:49:42 Provide additional details. Crash ID Chrome (Server ID: 0698f39c80000000) Automatically reported Wednesday, 8 February 2017 at 14:22:13 Provide additional details. Crash ID Chrome (Server ID: b9aeed9c80000000) Automatically reported Wednesday, 8 February 2017 at 13:20:51 Provide additional details. Crash ID Chrome (Server ID: 23c098d580000000) Automatically reported Wednesday, 8 February 2017 at 09:07:11 Provide additional details. Crash ID Chrome (Server ID: 2249975580000000) Automatically reported Tuesday, 7 February 2017 at 15:06:20 Provide additional details. Crash ID Chrome (Server ID: 87b3806c80000000) Automatically reported Monday, 6 February 2017 at 17:09:47 Provide additional details. Crash ID Chrome (Server ID: 50d57fac80000000) Automatically reported Monday, 6 February 2017 at 17:00:39 Provide additional details. Crash ID Chrome (Server ID: aed7355580000000) Automatically reported Monday, 6 February 2017 at 17:00:31 Provide additional details. Crash ID Chrome (Server ID: c9a13fac80000000) Automatically reported Monday, 6 February 2017 at 16:59:41 Provide additional details. Crash ID Chrome (Server ID: 363e155580000000) Automatically reported Monday, 6 February 2017 at 15:58:51 Provide additional details. Crash ID Chrome (Server ID: baa4852c80000000) Automatically reported Sunday, 5 February 2017 at 17:58:29 Provide additional details. Crash ID Chrome (Server ID: 7497565580000000) Automatically reported Sunday, 5 February 2017 at 11:51:25 Provide additional details. Crash ID Chrome (Server ID: 8660011880000000) Automatically reported Friday, 3 February 2017 at 18:05:05 Provide additional details. Crash ID Chrome (Server ID: 35f31ba880000000) Automatically reported Tuesday, 31 January 2017 at 15:33:36 Provide additional details. Crash ID Chrome (Server ID: 1ba1e6a880000000) Automatically reported Monday, 30 January 2017 at 21:24:39 Provide additional details. Crash ID Chrome (Server ID: 077c471580000000) Automatically reported Monday, 30 January 2017 at 21:15:38 Provide additional details. Crash ID Chrome (Server ID: 6358652880000000) Automatically reported Sunday, 29 January 2017 at 14:09:59 Provide additional details. Crash ID Chrome (Server ID: e3e8a52880000000) Automatically reported Sunday, 29 January 2017 at 14:01:15 Provide additional details. Crash ID Chrome (Server ID: 99f7252880000000) Automatically reported Sunday, 29 January 2017 at 13:59:48 Provide additional details. Crash ID Chrome (Server ID: 7e4fbe1580000000) Automatically reported Saturday, 28 January 2017 at 13:58:31 Provide additional details. Crash ID Chrome (Server ID: 8a7ac94680000000) Automatically reported Wednesday, 25 January 2017 at 13:28:08 Provide additional details. Crash ID Chrome (Server ID: cb92af8880000000) Automatically reported Tuesday, 24 January 2017 at 16:11:42 Provide additional details. Crash ID Chrome (Server ID: 1444e68880000000) Automatically reported Monday, 23 January 2017 at 12:37:50 Provide additional details. Crash ID Chrome (Server ID: e3f84ee580000000) Automatically reported Sunday, 22 January 2017 at 10:17:16 Provide additional details. Crash ID Chrome (Server ID: 89a410e580000000) Automatically reported Thursday, 19 January 2017 at 18:32:54 Provide additional details. Crash ID Chrome (Server ID: 09dfe0e580000000) Automatically reported Thursday, 19 January 2017 at 18:29:59 Provide additional details. Crash ID Chrome (Server ID: 3b49e0e580000000) Automatically reported Thursday, 19 January 2017 at 18:20:35 Provide additional details. Crash ID Chrome (Server ID: f352e0e580000000) Automatically reported Thursday, 19 January 2017 at 18:14:52 Provide additional details. Crash ID Chrome (Server ID: 818fadfa80000000) Automatically reported Thursday, 19 January 2017 at 09:04:05 Provide additional details. Crash ID Chrome (Server ID: 806fbe6580000000) Automatically reported Monday, 16 January 2017 at 18:56:07 Provide additional details. Crash ID Chrome (Server ID: 8b43e97080000000) Automatically reported Monday, 16 January 2017 at 18:20:40 Provide additional details. Crash ID Chrome (Server ID: 2067697080000000) Automatically reported Monday, 16 January 2017 at 18:13:26 Provide additional details. Crash ID Chrome (Server ID: dbb8447080000000) Automatically reported Sunday, 15 January 2017 at 14:35:21 Provide additional details. Crash ID ChromeOS (Server ID: 54338db080000000) Automatically reported Saturday, 14 January 2017 at 09:34:01 Provide additional details. Crash ID Chrome (Server ID: 993aaaba80000000) Automatically reported Friday, 13 January 2017 at 20:33:43 Provide additional details. Crash ID Chrome (Server ID: e86222b080000000) Automatically reported Friday, 13 January 2017 at 11:04:05 Provide additional details. Crash ID Chrome (Server ID: 4f0f9fa580000000) Automatically reported Friday, 13 January 2017 at 08:59:18 Provide additional details. Crash ID Chrome (Server ID: 6792b8a480000000) Automatically reported Tuesday, 10 January 2017 at 21:29:30 Provide additional details. Crash ID Chrome (Server ID: a62c5d5080000000) Automatically reported Sunday, 8 January 2017 at 10:53:46 Provide additional details. Crash ID Chrome (Server ID: 43879d5080000000) Automatically reported Sunday, 8 January 2017 at 10:45:28 Provide additional details. Crash ID Chrome (Server ID: 268a9d5080000000) Automatically reported Sunday, 8 January 2017 at 10:37:56 Provide additional details. Crash ID Chrome (Server ID: bd7c1dc480000000) Automatically reported Saturday, 7 January 2017 at 12:13:21 Provide additional details.
,
Feb 15 2017
Here are my last 50 crashes as listed on chrome://crashes Crashes Start uploading crashes Crashes (50) Crash ID Chrome (Server ID: ed31b39040000000) Automatically reported Monday, February 13, 2017 at 9:27:56 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fed31b39040000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 258e343580000000) Automatically reported Monday, February 13, 2017 at 9:21:30 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F258e343580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 2c0b781280000000) Automatically reported Sunday, February 12, 2017 at 10:20:08 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F2c0b781280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 01d3d81280000000) Automatically reported Sunday, February 12, 2017 at 10:13:58 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F01d3d81280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: d29d581280000000) Automatically reported Sunday, February 12, 2017 at 10:12:30 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fd29d581280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 150b583580000000) Automatically reported Sunday, February 12, 2017 at 10:10:19 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F150b583580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 64a5846040000000) Automatically reported Sunday, February 12, 2017 at 4:21:31 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F64a5846040000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: ce829dd580000000) Automatically reported Friday, February 10, 2017 at 1:08:32 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fce829dd580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: a44d1dd580000000) Automatically reported Friday, February 10, 2017 at 1:04:29 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fa44d1dd580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 6e361dd580000000) Automatically reported Friday, February 10, 2017 at 12:58:00 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F6e361dd580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 7b64bcc280000000) Automatically reported Friday, February 10, 2017 at 12:50:43 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F7b64bcc280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 6d8a6cfc80000000) Automatically reported Thursday, February 9, 2017 at 10:49:50 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F6d8a6cfc80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: eac4ecfc80000000) Automatically reported Thursday, February 9, 2017 at 10:47:34 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Feac4ecfc80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: a39e28dc80000000) Automatically reported Wednesday, February 8, 2017 at 7:47:00 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fa39e28dc80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: ae4cf0dc80000000) Automatically reported Wednesday, February 8, 2017 at 7:39:07 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fae4cf0dc80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 19cfc8d580000000) Automatically reported Wednesday, February 8, 2017 at 12:19:47 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F19cfc8d580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 20fa729c80000000) Automatically reported Wednesday, February 8, 2017 at 12:14:52 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F20fa729c80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 611f7b7380000000) Automatically reported Wednesday, February 8, 2017 at 12:05:21 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F611f7b7380000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: f118406c80000000) Automatically reported Monday, February 6, 2017 at 12:12:58 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Ff118406c80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: d323b55580000000) Automatically reported Monday, February 6, 2017 at 12:06:49 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fd323b55580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 30ad7fac80000000) Automatically reported Monday, February 6, 2017 at 12:03:42 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F30ad7fac80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 79f082ac80000000) Automatically reported Sunday, February 5, 2017 at 9:33:08 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F79f082ac80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 14f680ac80000000) Automatically reported Sunday, February 5, 2017 at 6:06:34 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F14f680ac80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 10d4c15580000000) Automatically reported Sunday, February 5, 2017 at 6:02:46 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F10d4c15580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 86780e5580000000) Automatically reported Sunday, February 5, 2017 at 10:02:17 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F86780e5580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 5dea3a2c80000000) Automatically reported Sunday, February 5, 2017 at 9:00:00 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F5dea3a2c80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 70feddcc80000000) Automatically reported Saturday, February 4, 2017 at 6:31:50 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F70feddcc80000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: dd1e3ae980000000) Automatically reported Saturday, February 4, 2017 at 6:30:56 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fdd1e3ae980000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 324f709880000000) Automatically reported Friday, February 3, 2017 at 8:23:44 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F324f709880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 47198c5580000000) Automatically reported Friday, February 3, 2017 at 4:50:26 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F47198c5580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 1092ad1880000000) Automatically reported Friday, February 3, 2017 at 3:45:04 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F1092ad1880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 3a48f45580000000) Automatically reported Friday, February 3, 2017 at 3:42:26 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F3a48f45580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 93fcc3a980000000) Automatically reported Friday, February 3, 2017 at 3:39:01 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F93fcc3a980000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 344d985580000000) Automatically reported Friday, February 3, 2017 at 8:15:36 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F344d985580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: e94e985580000000) Automatically reported Friday, February 3, 2017 at 8:09:06 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fe94e985580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 9c13441880000000) Automatically reported Friday, February 3, 2017 at 8:04:56 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F9c13441880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 3bd0589580000000) Automatically reported Tuesday, January 31, 2017 at 7:29:51 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F3bd0589580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: ab08046880000000) Automatically reported Tuesday, January 31, 2017 at 7:22:13 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fab08046880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: d88c321680000000) Automatically reported Tuesday, January 31, 2017 at 7:17:36 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fd88c321680000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: e460f86880000000) Automatically reported Tuesday, January 31, 2017 at 7:11:43 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fe460f86880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 3082786880000000) Automatically reported Tuesday, January 31, 2017 at 7:01:52 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F3082786880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 30d8521680000000) Automatically reported Tuesday, January 31, 2017 at 6:58:28 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F30d8521680000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 451f1d5300000000) Automatically reported Tuesday, January 31, 2017 at 3:39:57 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F451f1d5300000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 6073906880000000) Automatically reported Tuesday, January 31, 2017 at 3:37:18 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F6073906880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 87e54c1680000000) Automatically reported Tuesday, January 31, 2017 at 3:27:46 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F87e54c1680000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: f203d09580000000) Automatically reported Tuesday, January 31, 2017 at 1:37:42 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Ff203d09580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: ec47b7a880000000) Automatically reported Tuesday, January 31, 2017 at 12:32:19 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fec47b7a880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 981b301680000000) Automatically reported Tuesday, January 31, 2017 at 11:19:19 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F981b301680000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 315bf82880000000) Automatically reported Saturday, January 28, 2017 at 9:39:05 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F315bf82880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 4001782880000000) Automatically reported Saturday, January 28, 2017 at 9:32:31 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F4001782880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted>
,
Feb 16 2017
This problem seems to be at its worse with the Asus Flip C100a I found several forums where people are experiencing the same thing especially with the track-pad and they all seem to have started around the same time period https://productforums.google.com/forum/#!topic/chromebook-central/e2MAzw-AgMs https://productforums.google.com/forum/#!topic/chromebook-central/8qOFJsoZtJw;context-place=forum/chromebook-central https://www.reddit.com/r/chromeos/comments/5m89b0/aw_snap_problem_w_asus_chrombook_flip_c100padb02/ https://www.reddit.com/r/chromeos/comments/4pqgoe/asus_chromebook_flip_version_53027733_dev/ https://www.amazon.co.uk/ASUS-Chromebook-C100PA-Chrome-Touchscreen/product-reviews/B0107N7WT6?pageNumber=4 (search reviews for snap) https://scratch.mit.edu/discuss/topic/179021/?page=2 https://www.amazon.com/forum/-/Tx334NYYXWE2Y65/ref=ask_ql_ql_al_hza?asin=B00YY3X678
,
Feb 17 2017
hjsanson@gmail.com and susanr222@gmail.com. Thank you. I'm seeing a lot of crashes in the extension process there. Have you tried disabling extensions to see if things improve? Unfortunately, the analysis backend is bisbehaving at the moment so I'm not able to dig deep into the details of the crashes themselves (other than to see at a very high level where they are). I'll take another look once the tool is working again.
,
Feb 17 2017
Re: Comment #63 on issue 651989 by abodenha@chromium.org: Lots of Aw snaps in the latest Chrome build https://bugs.chromium.org/p/chromium/issues/detail?id=651989#c63 I already disabled all nonessential extensions. Here are some additional crashes (a lot on Facebook) (Note that because of this problem I am only using the Chromebook intermittently, otherwise you would see a lot more crashes listed): Crash ID Chrome (Server ID: 626cf0e240000000) Automatically reported Thursday, February 16, 2017 at 11:35:19 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F626cf0e240000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: f730c53580000000) Automatically reported Wednesday, February 15, 2017 at 2:06:24 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Ff730c53580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 5229aff280000000) Automatically reported Wednesday, February 15, 2017 at 1:15:15 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F5229aff280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: d73b4ff280000000) Automatically reported Wednesday, February 15, 2017 at 1:10:24 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fd73b4ff280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 136d8ff280000000) Automatically reported Wednesday, February 15, 2017 at 1:10:04 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F136d8ff280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 9236f93580000000) Automatically reported Wednesday, February 15, 2017 at 1:00:57 PM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F9236f93580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 7c79bcf280000000) Automatically reported Wednesday, February 15, 2017 at 10:08:46 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F7c79bcf280000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted> Crash ID Chrome (Server ID: 573711e840000000) Automatically reported Wednesday, February 15, 2017 at 10:02:22 AM Provide additional details <https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2055.0.2883.105%0AOperating%20System%3A%20Linux%203.14.0%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F573711e840000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted>
,
Feb 17 2017
I also have problems with chrome and the trackpad on the Asus flip. I've done all the suggested troubleshooting. It seems that it may be an issue with the device model. Is this possible or has this been explored? Mine is over a year old so I would not have any warranty.
,
Feb 18 2017
there are many of us with the chromebooks having this problem. I wish I could give you a list of all the crashes I have experienced. I know you mean well by asking about extensions, but truly, we have been experiencing this problem for many months now. Most of us have done everything under the sun possible from our side to rectify the problem, and many have just totally given up on the chromebook. These chromebooks were awesome, they worked fast and well, then suddenly they are practically useless. I'm glad that you are finally seeing that the problem is resolving around the chromebooks. Chrome does not hardly ever crash on my android phone, or my apple computer, only on this chromebook.
,
Feb 18 2017
Hi I'm with Wheesh. I have disabled extensions (bar 1 Ad blocker the rest are all to do with Google e.g. docs and unless they're enabled the products won't work), I have reset, powerwashed, disabled the touchpad and USB, used the touch screen only and so on and so forth yet nothing changes. In fact yesterday it went up a notch- the touchpad stops working completely- it stops clicking. It happens in particular when I use Google Docs or spreasdsheet and I left click and instead of crashing the tab it now freezes whatever I'm doing and the touchpad cannot click. I can stop it briefly by going into touch screen mode or using a mouse. I love(d) this chromebook. I have had mine for a while and as I've stated it was fine up until the update that put google store on it and from then on it has been a living hell. I know you mean well but I feel I'm going around in circles that every time people like me ask for help we are told the same old things or worst (which happens a lot on the Google support pages) are told it's our fault... but how can so many people facing the same issues on the same machines all be doing something wrong at the same time. My machine has just gone (in the last 2 weeks) of the warranty period but I'm not convinced that it is at fault as I've had it so long without issue and it also happens on other machines as well on a regular basis. I know there's not a simple overnight solution but if we know that helps is on the way we wouldn't feel so despondent.
,
Feb 18 2017
This is a long shot but I have contacted ASUS technical support and have copied all the threads about this problem in the vain hope they do something. I will keep you updated with how I get on
,
Feb 18 2017
One thing that would be super interesting is to try a memory test, just to make sure. The one built-in isn't amazing, but it will catch if you have serious memory problems. Go to crosh (Ctrl-Alt-T) and use the command memory_test If it reports errors then that is likely the root problem.
,
Feb 18 2017
Thank you for this suggestion, but I have done this as well.
,
Feb 19 2017
@70 one loop that's only testing 62M of memory isn't nearly enough. I'd suggest rebooting your laptop and making sure all tabs are closed to give it the most memory. Then run the test overnight (8-12 hours or so) to look for problems.
,
Feb 22 2017
Just adding my angst to this issue. here's the text of my last feedback to the last (of 100's) of feedback reports I sent with the "aw snap" tab crash issue... I am so profoundly tired and frustrated with the increasing frequency of crashes that started late last year. From the forums, it is clearly a known issue, so it is doubly frustrating that nothing has been done to fix it. Even worse the lack of response to the hundreds of these feedback reports I have generated. I have tried everything - unloading extensions, powerwashing, resets, moving to dev channels (ie v58) to no avail. Incidently, I have even had a tab crash on loading just the browser home tab straight after a powerwash... in fact, while I have been I writing this just I have had 3 separate tab crashes - one a background tab (with google doc home screen) and this tab has crashed twice while trying to write this. (check your feedback logs) I concur with some of the comments on this thread in that tab crashes are always immediately preceded by erratic bluetooth mouse/trackpad behaviour. Less predictable are how many tabs will crash along with it. This is definitely an introduced issue - I have has my Asus Flip since early 2016, and it only became apparent towards the end of 2016, and has noticeably become more frequent. As it stands, the frequency and unpredictability of this issue renders my chromebook almost unusable and now unsure about continuing with it. For the record, I am currently on following: Chrome version 55.0.2883.105 ChromeOS version 8872.76.0 Channel "stable" (...joke!) Platform 8872.76.0 (Official Build) stable-channel veyron_minnie ARC Version 3617689 Firmware Google_Veyron_Minnie.6588.197.0
,
Feb 22 2017
I have had a response for ASUS who are basically washing their hands of the issue and passed the buck to Google. They did give me a number for Google which was great given the one they publish online is a joke. They claim they are going to pass this onto the Chromebook team so it's a case of watch this space. My touchpad issue is so troubling that I dare not touch it as the slightest press is now triggering the aw snaps in abundance. It is at it's worst when using Docs or Sheets. I am going to run another memory test but something tells me this will be a waste of time.
,
Feb 22 2017
Looks like the issue is related to https://bugs.chromium.org/p/chromium/issues/detail?id=690517 ? A memory leak is possibly making the memory issue from bad to worse recently. Other than the memory leak, the tab discarder was not functioning properly: https://bugs.chromium.org/p/chromium/issues/detail?id=645512 I've submitted a fix for that and merging them back to M57. I believe things will get better after the two issues mentioned above are resolved.
,
Feb 26 2017
On this forum https://productforums.google.com/forum/#!topic/chromebook-central/8qOFJsoZtJw;context-place=forum/chromebook-central Someone has claimed that 'It appears that this issue has been fixed by Google. Since updating to Version 57.0.2987.59 beta "Aw, Snap!" has never happened on my Flip. Hope so. Read the other day that Google fixed an issue with the Trackpad with their own Samsung Chromebook.' There is no evidence to support their first claim re: 57.0.2987.59- unless you can confirm this is true but the second part has some credence as if you search for this there is evidence that some Samsung machine in the past and currently have suffered from the same problem but there is no talk of a fix. However the problems with the Samsung machines stretch back as far as 2011! So this is not a new phenomenon so you would have thought after 6 years this type of thing would not still be happening
,
Mar 1 2017
56.0.2924.110 is now live for the ARC++ capable machines. Can people who are seeing frequent Aw, Snaps please update? I can't promise it fixes the problems you're seeing but it should allow us to collect data we can use to further investigate.
,
Mar 1 2017
bug 697521 is making investigation here difficult.
,
Mar 1 2017
Updated this morning at 11:30 am > let the Asus Flip do it's thing for a while ie. finish with the Arc++ loading > opened web Inbox > a nice Aw Snap. I've since opened Inbox several times. It is incredibly slow to load compared to the Acer 15 i5, but at least it does work and opens emails after a while. Looking at the task manager > CPU above 100 several times for Inbox tab and browser. Crash ID Chrome (Server ID: 363e873300000000) Automatically reported Wednesday, March 1, 2017 at 11:36:53 AM 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
,
Mar 1 2017
Thanks dymphep@. That one looks like some extension caused the javascript engine to crash. I've filed bug 697563 to track.
,
Mar 2 2017
Since this problem had persisted for so long, I followed one of the commenter's suggestion and switched to the beta version a couple days ago. I experienced a few crashes, not worse and perhaps a bit better than before. I decided to try switching back to the "stable" version last night which required me to powerwash when I logged back in today. So now I'm on: 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 which was released in February. The result: now, I have had multiple repeated crashes in the past several minutes! And just now, when I wanted to check the exact date of this version's release, my Settings page crashed! Although this gmail page did not. Can anyone tell the estimated time of arrival of a fix?
,
Mar 2 2017
Comment #57 contains additional data relevant to this bug. Not sure why it was deleted. I've restored it. As I said (poorly) in #53 I suspect multiple issues. If beta channel looks more stable that bodes well for cylee@'s tab discarder fix being a major component. Ongoing investigation in bug 696055 and bug 690517 make me think this MIGHT also be related. As such, going into drive.google.com, hitting settings and turning off offline sync might help.
,
Mar 2 2017
the previous beta version to the update version below resolved "aw snap" on my asus flip - no tab crashes all week - but now back to regular tab crashes. Version 57.0.2987.85 beta Platform 9202.43.0 (Official Build) beta-channel veyron_minnie ARC Version 3768718 Firmware Google_Veyron_Minnie.6588.237.0
,
Mar 16 2017
tab crashes still occurring regularly... new crash behaviour: - no longer seems to be preceded by pointer freezing/stuttering, just crashes - google inbox tabs (multiple gmail accounts) crash simultaneously in background version before 57.0.2987.85 resolved issues, but subsequent two beta updates have resulted in recurrence of aw snap problems (reverting to stable version is worse) current version: Version 57.0.2987.100 beta Platform 9202.51.0 (Official Build) beta-channel veyron_minnie ARC Version 3794798 Firmware Google_Veyron_Minnie.6588.237.0 Crash ID Chrome (Server ID: 4e5f495520000000) Crash report uploaded on Thursday, 16 March 2017 at 12:04:04 Provide additional details. Crash ID ChromeOS (Server ID: 3a50adea60000000) Crash report uploaded on Wednesday, 15 March 2017 at 17:00:29 Provide additional details. Crash ID Chrome (Server ID: 0a5c41ea60000000) Crash report uploaded on Wednesday, 15 March 2017 at 16:12:25 Provide additional details. Crash ID Chrome (Server ID: 312cbeea60000000) Crash report uploaded on Wednesday, 15 March 2017 at 16:03:15 Provide additional details. Crash ID Chrome (Server ID: 7203deea60000000) Crash report uploaded on Wednesday, 15 March 2017 at 16:03:03 Provide additional details. Crash ID Chrome (Server ID: 8fc8f6e480000000) Crash report uploaded on Wednesday, 15 March 2017 at 15:56:30 Provide additional details.
,
Mar 16 2017
Updated to 56 in February, and things seemed ok- at first. However things have started to get bad again and yesterday whilst working in Docs (which was always one of the worst for causing them), the aw snaps came back in abundance. However, doesn't seem to be triggered by the touchpad as much- just appears to be random. Have copied my crashes. 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 Crash ID Chrome (Server ID: 4a9d0b2d80000000) Automatically reported Wednesday, 15 March 2017 at 20:38:36 Provide additional details. Crash ID Chrome (Server ID: e968b2a520000000) Automatically reported Wednesday, 15 March 2017 at 14:48:47 Provide additional details. Crash ID Chrome (Server ID: dd954d2d80000000) Automatically reported Wednesday, 15 March 2017 at 14:45:27 Provide additional details. Crash ID Chrome (Server ID: e40ce25a60000000) Automatically reported Wednesday, 15 March 2017 at 14:37:49 Provide additional details. Crash ID Chrome (Server ID: 8709bee480000000) Automatically reported Wednesday, 15 March 2017 at 14:34:36 Provide additional details. Crash ID Chrome (Server ID: d42500a520000000) Automatically reported Wednesday, 15 March 2017 at 14:26:17 Provide additional details. Crash ID Chrome (Server ID: 91df73f4a0000000) Automatically reported Sunday, 12 March 2017 at 12:56:44 Provide additional details. Crash ID Chrome (Server ID: 918a722820000000) Automatically reported Sunday, 12 March 2017 at 12:47:11 Provide additional details. Crash ID Chrome (Server ID: 7774536480000000) Automatically reported Friday, 10 March 2017 at 16:23:40 Provide additional details. Crash ID Chrome (Server ID: 9aef3d5120000000) Automatically reported Tuesday, 7 March 2017 at 19:57:02 Provide additional details. Crash ID Chrome (Server ID: a7fa72e120000000) Automatically reported Tuesday, 7 March 2017 at 08:35:47 Provide additional details. Crash ID Chrome (Server ID: dd932e7580000000) Automatically reported Saturday, 4 March 2017 at 15:27:16 Provide additional details. Crash ID Chrome (Server ID: 416adb3cc0000000) Automatically reported Monday, 27 February 2017 at 16:16:42 Provide additional details. Crash ID Chrome (Server ID: 4d49a63cc0000000) Automatically reported Monday, 27 February 2017 at 15:18:42 Provide additional details. Crash ID Chrome (Server ID: fdfdded1c0000000) Automatically reported Monday, 27 February 2017 at 15:11:36 Provide additional details. Crash ID Chrome (Server ID: ed450c7580000000) Automatically reported Sunday, 26 February 2017 at 10:16:05 Provide additional details. Crash ID ChromeOS (Server ID: 7c7c2921c0000000) Automatically reported Sunday, 26 February 2017 at 08:18:42 Provide additional details. Crash ID Chrome (Server ID: 17ff1d3f40000000) Automatically reported Wednesday, 22 February 2017 at 20:54:05 Provide additional details. Crash ID Chrome (Server ID: a3d399d300000000) Automatically reported Tuesday, 21 February 2017 at 20:42:28 Provide additional details. Crash ID Chrome (Server ID: 1c3d4eb580000000) Automatically reported Tuesday, 21 February 2017 at 08:25:02 Provide additional details. Crash ID Chrome (Server ID: 9a9f62b580000000) Automatically reported Sunday, 19 February 2017 at 21:55:12 Provide additional details. Crash ID Chrome (Server ID: 9ae5009440000000) Automatically reported Saturday, 18 February 2017 at 15:27:59 Provide additional details. Crash ID Chrome (Server ID: c52f3d1440000000) Automatically reported Saturday, 18 February 2017 at 14:21:29 Provide additional details. Crash ID Chrome (Server ID: 9b777d3580000000) Automatically reported Thursday, 16 February 2017 at 10:42:25 Provide additional details. Crash ID Chrome (Server ID: f5f3113580000000) Automatically reported Wednesday, 15 February 2017 at 08:30:01 Provide additional details. Crash ID Chrome (Server ID: 32649c3580000000) Automatically reported Monday, 13 February 2017 at 18:34:27 Provide additional details. Crash ID Chrome (Server ID: a01dee5040000000) Automatically reported Monday, 13 February 2017 at 17:12:30 Provide additional details. Crash ID Chrome (Server ID: 1d1cbe4f80000000) Automatically reported Saturday, 11 February 2017 at 08:18:00 Provide additional details. Crash ID Chrome (Server ID: 8cc7ee4f80000000) Automatically reported Saturday, 11 February 2017 at 08:14:24 Provide additional details. Crash ID Chrome (Server ID: 95af0cc280000000) Automatically reported Friday, 10 February 2017 at 17:26:45 Provide additional details. Crash ID Chrome (Server ID: a743ead580000000) Automatically reported Thursday, 9 February 2017 at 09:22:55 Provide additional details. Crash ID Chrome (Server ID: 0668e2bc80000000) Automatically reported Thursday, 9 February 2017 at 09:15:38 Provide additional details. Crash ID Chrome (Server ID: d02f0e5c80000000) Automatically reported Wednesday, 8 February 2017 at 19:49:42 Provide additional details. Crash ID Chrome (Server ID: 0698f39c80000000) Automatically reported Wednesday, 8 February 2017 at 14:22:13 Provide additional details. Crash ID Chrome (Server ID: b9aeed9c80000000) Automatically reported Wednesday, 8 February 2017 at 13:20:51 Provide additional details. Crash ID Chrome (Server ID: 23c098d580000000) Automatically reported Wednesday, 8 February 2017 at 09:07:11 Provide additional details. Crash ID Chrome (Server ID: 2249975580000000) Automatically reported Tuesday, 7 February 2017 at 15:06:20 Provide additional details. Crash ID Chrome (Server ID: 87b3806c80000000) Automatically reported Monday, 6 February 2017 at 17:09:47 Provide additional details. Crash ID Chrome (Server ID: 50d57fac80000000) Automatically reported Monday, 6 February 2017 at 17:00:39 Provide additional details. Crash ID Chrome (Server ID: aed7355580000000) Automatically reported Monday, 6 February 2017 at 17:00:31 Provide additional details. Crash ID Chrome (Server ID: c9a13fac80000000) Automatically reported Monday, 6 February 2017 at 16:59:41 Provide additional details. Crash ID Chrome (Server ID: 363e155580000000) Automatically reported Monday, 6 February 2017 at 15:58:51 Provide additional details. Crash ID Chrome (Server ID: baa4852c80000000) Automatically reported Sunday, 5 February 2017 at 17:58:29 Provide additional details. Crash ID Chrome (Server ID: 7497565580000000) Automatically reported Sunday, 5 February 2017 at 11:51:25 Provide additional details. Crash ID Chrome (Server ID: 8660011880000000) Automatically reported Friday, 3 February 2017 at 18:05:05 Provide additional details. Crash ID Chrome (Server ID: 35f31ba880000000) Automatically reported Tuesday, 31 January 2017 at 15:33:36 Provide additional details. Crash ID Chrome (Server ID: 1ba1e6a880000000) Automatically reported Monday, 30 January 2017 at 21:24:39 Provide additional details. Crash ID Chrome (Server ID: 077c471580000000) Automatically reported Monday, 30 January 2017 at 21:15:38 Provide additional details. Crash ID Chrome (Server ID: 6358652880000000) Automatically reported Sunday, 29 January 2017 at 14:09:59 Provide additional details. Crash ID Chrome (Server ID: e3e8a52880000000) Automatically reported Sunday, 29 January 2017 at 14:01:15 Provide additional details.
,
Mar 17 2017
hjsanson@: Hopefully the end is in sight! It actually looks like your problems are stack overflow related and we're hot on the trail of that. Unfortunately someone marked the main bug tracking this (bug #665083) as Restricted (sigh), but a quick summary: * For whatever reason, Chromebook Flip seems to be hitting these stack overflows a lot, but other machines don't. * This is a stack overflow of a thread in Chrome. * Prior to some kernel changes we just landed in M-57 it was very hard to track down these stack overflows. There are still some issues tracking them down, but we have hope now. At this point I'm waiting for the kernel change to roll out more widely so I can analyze some of the crashes better...
,
Mar 17 2017
FYI that the beta channel is live with the fix that will give us a better chance to debug these stack overflows. If you've got: 9202.53.0 / 57.0.2987.112 ...then start trying to reproduce. When you do, upload those crash reports right away. I'll search for relevant crash periodically during the day to see if any have rolled in that give the debugging info we need.
,
Mar 17 2017
I think if I understand, you want me to switch to version beta version 57? Do I do that by going to settings and changing the channel to beta Or Do I use the version that can be found on Google Play (this now say 58) I am so glad that the flipbook may resume to business as normal sometime soon
,
Mar 17 2017
Yeah, if you change the channel to "beta" it will update to M-57. Of course, you should understand that (in general) beta channel is less stable than stable channel. ...and if you want to switch back it might require your device to get reset back to factory state. At the moment, though, one of your existing crashes gave me a clue that I'm trying to follow up on. ...so maybe if you don't want to play with beta you should just wait...
,
Mar 17 2017
So this is a bit of a generic bug, but since the last few have been about crashes on Chromebook Flip, co-opting it for now. Based on digging and on the new debug info already reported from the latest beta channel, we have a candiate stack overflow. We've got infinite recursion with: 0x300b5a77 (chrome -VisualViewport.cpp:181 ) blink::VisualViewport::clampToBoundaries() 0x300b5ba7 (chrome -VisualViewport.cpp:289 ) blink::VisualViewport::didSetScaleOrLocation(float, blink::FloatPoint const&) 0x300b5a2f (chrome -VisualViewport.cpp:242 ) blink::VisualViewport::setScaleAndLocation(float, blink::FloatPoint const&) 0x300b5a77 (chrome -VisualViewport.cpp:181 ) blink::VisualViewport::clampToBoundaries() 0x300b5ba7 (chrome -VisualViewport.cpp:289 ) blink::VisualViewport::didSetScaleOrLocation(float, blink::FloatPoint const&) 0x300b5a2f (chrome -VisualViewport.cpp:242 ) blink::VisualViewport::setScaleAndLocation(float, blink::FloatPoint const&) 0x300b5a77 (chrome -VisualViewport.cpp:181 ) blink::VisualViewport::clampToBoundaries() We still can't reproduce yet, but according the the dev who works on this code, it's related to pinch-zoom and scrolling. If anyone who can reproduce can use this to find some nice steps, that'd be great. Specifically: 1. Tablet mode, or laptop mode? 2. Do you use pinch to zoom on the screen? 3. Did you just scroll using the touchscreen, or scroll some other way? 4. Any particular pages that reproduce this? 5. Task bar showing? Bookmark bar showing? 6. Any special zoom mode on the page? Do you use Ctrl + or Ctrl - to zoom in and out too? 7. What do you have your screen resolution set to?
,
Mar 17 2017
For people experiencing the crashes on Chromebook Flip, best place to discuss is probably bug #702771
,
Mar 18 2017
To answer your question. 1. laptop mode 2. it happens without pinching or zooming. It was happening so often, so there were so me times that I had used pinching and zooming, but certainly MANY, many times it happened without my doing that 3. scrolled down using touchpad 4. happened frequently in google docs, but also happened on many other sites 5. task bar is showing ( well if I'm correct about what a taskbar is) the bookmark bar is not showing unless I was opening up a new tab, then it appears on that page 6. I have never used Ctrl plus or minus to zoom in or out 7. I have never changed the original settings for resolution. Please tell me how to find out and I will tell you. If you mean the information listed under advance settings for web content....font size- medium, page zoom 100% I hope that can help in some way.
,
Mar 21 2017
As a heads up for anyone following Chromebook Flip issues (the last several comments): we are continuing to make progress in bug #702771 . This is the last update I'll post about it here since this bug is about lots of different stuff. Anyone interested in continuing to get information should star bug #702771 to get updates.
,
Mar 29 2017
There's a new build on beta for the flip (58.0.3029.31) that we're hoping resolves many of the aw, snaps that people are seeing. Can someone give it a shot and let us know if the situation is improved?
,
Mar 29 2017
I would love to do this, but I can't figure out how. Could you explain a bit. I tried going to the chrome web store, and the beta google play . ( the beta google play isn't working at all) . Thank you for your help and for trying to solve this problem. It will be wonderful if we can actually use our chromebooks again.
,
Mar 29 2017
wheesh@ Click on the status area bottom right ot 3 dot menu top right Settings > click on the blue about chrome os > click on the blue "more info" > change channel Or type chrome://chrome in the address bar
,
Mar 29 2017
Thank you. I did as you said and I was already on 58.0.3029.31 beta. I don't know if this build started this morning, as I did totally shut down my machine last night. If , however, it is not new from this morning, then I would have to say that I had quite a few problems last night. Ended up frustrated and just shut down the machine. Hopefully this is new this morning. I will report back later.
,
Mar 30 2017
so far so good - no "aw snaps" since yesterday afternoon (GMT+11) upgrade Version 58.0.3029.31 beta Platform 9334.18.0 (Official Build) beta-channel veyron_minnie ARC Version 3836087 Firmware Google_Veyron_Minnie.6588.237.0 last crash (of about 50) for the past week: Crash ID ChromeOS (Server ID: cc02046360000000) Crash report uploaded on Wednesday, 29 March 2017 at 15:26:29 keeping fingers crossed for now
,
Mar 30 2017
used my chromebook flip for at least an hour today- didn't have one problem. This is good! very hopeful!
,
Mar 31 2017
no crashes yesterday or today! that has happened for over a year! Thank you!
,
Mar 31 2017
day 2 no snaps - woohoo! thanks
,
Mar 31 2017
IMHO let's close this. * As per comment 56, having one bug to talk about all crashes ins't too useful. * The crashes related to Chromebook Flip are tracked in bug #702771 * If there are other crashes they should get other bugs filed for them.
,
Apr 3 2017
Agreed.
,
Apr 6 2017
No crashes in over a week, since I went on 58 beta. I am currently on Version 58.0.3029.40 beta Platform 9334.28.0 (Official Build) beta-channel veyron_minnie ARC Version 3857639 Firmware Google_Veyron_Minnie.6588.237.0 I'm thrilled, hope this lasts. I'm impressed by the dedication and responsiveness of those involved. Thank you. Keeping fingers crossed, as I love my ASUS flip.
Showing comments 5 - 104
of 104
Older ›
|
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
