My problem may seem a bit vague (it is to me too), but here is my attempted explanation of it.
A few months ago, I implemented PDF.js in my web application. It was really useful, and I am using it for interactions with my clients.
Suddenly, last week, my clients reported to me "Aw, Snap" messages in Google Chrome on their PCs when they try to launch PDF.js. I have an iMac and two PCs at home, so I decided to test this out.
When I used Google Chrome on my iMac to launch PDF.js, I found it worked fine.
When I used Google Chrome on my first PC to launch PDF.js, I found it worked fine.
When I used Google Chrome on my second PC to launch PDF.js, even though it previously worked, it kept crashing and showing me "Aw, Snap" messages.
This was weird. I tried removing all the extensions, clearing the cache, clearing the LocalStorage, but nothing seemed to fix the problem.
I then realised, after some communication with my clients, launching PDF.js in Safari, Torch, Opera or Firefox on any operating system worked perfectly fine.
Why would this happen? I am using the web viewer in PDF.js. I also tried with the basic hello world example, but that broke as well (which I now find really weird), so I suspect there's something wrong with the rendering engine.
I also tried including the compatibility.js file after building the source, but with no avail.
Is there any known bug which causes Google Chrome tabs to crash?
Yes, I got it now.
From https://github.com/mozilla/pdf.js/issues/4104, I found the answer (thanks Rob and PDF.js dev team!). Take a look yourself!
I'm only posting this here so that anyone who stumbles upon this post with a similar problem can be helped (as this error took me quite a while to figure out).
Unfortunately, this does not seem to be the case. We've tried the latest version of pdf.js from github, also tried Chrome 33 (stable) which should have their V8 fix included and it still crashes. Also, tried the pdf.js commit mentioned in github thread (4ce6cb8 - https://github.com/mozilla/pdf.js/commit/4ce6cb8b0fa9db948516b2b738fa1503cf0ef90e) - still crashes. Also tried latest Chrome Canary available on 19/03/2014 - crash is there.
We can provide the WinDbg memory dump if it's of any help.
PS: sorry, this should be the answer to Rob W thread right above but I cannot add it there due to 0 reputation.
Related
Been googling around a bit for the last week or two and haven't come up with any leads.
I believe this started ever since the latest major chrome web browser update, from 68 to 69. (currently on version 69.0.3497.100 )
Basically, when I'm using the chrome dev tools and debugging some javascript, the browser crashes when I begin typing a variable name into the console. I'll get a character or two in and then bam, the whole thing crashes.
I'll close the browser, reopen it and still crashes immediately when typing in the console. Sometimes there are a few hours in between episodes, but this has been a persistent issue for too long and is severely impacting my ability as a developer.
Any help would be greatly appreciated. Thanks.
As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".
While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)
a long time we are developing one webapplication, that was running fine on Chrome 56. After Chrome upgrade on version 57.0.2987.* we are encountering a big problem. Sometimes if I'm moving with mouse, some errors will apears:
when this erros will apears, we cannot click on some functions like this:
it will generate another error:
so our application is in this state useless.
However, after refresh is all fine, after another refresh can this errors apears again. We don't know how to exactly simulate this bug.
Did someone encounter any similar problem?
PS: I'm not developer of this webapp, but if you need any other info, just ask. First I was asking here
Edit: On chrome 56 it works, on beta chrome 58 it works too without these errors.
It was just creepy version of Chrome. These errors was only on Chrome version 57. Other versions are ok. Even Google released version 58 faster, then it was expected.
For a while I've been trying to run a JavaScript CPU profile of some applications I've developed, but everytime I start running the JavaScript CPU profiler in Chrome Dev tools, the application will stop responding at all (same as the profiler).
However, I noticed that this is not specific to my application, since I've been able to reproduce the same problem in other popular applications like Travis-CI.
I've been suspecting of extensions and plugins, but running without them doesn't seem to make a different -- the problem persists.
I've tested simpler apps with the same technology (the To-Do MVC example built in EmberJS) and that profile works just as fine.
I'm currently using Chrome 40.0.2214.111 m (64-bit).
Any idea on what the problem may be?
Update: I've tested both under incognito and guest browser mode. I thought the guest browser made a difference because I was able to profile my application once without problems. However, trying that again proved that the problem still persists.
Furthermore, I've found that the freezing time does not seem to be related with the application itself. Sometimes it'll hang when I focus an element, sometimes when I move around, some other times when I am in the middle of writing into a textbox. There seems to be nothing specific about the functionality of the app that's triggering this.
I've also tried disabling most extensions, without luck. I'll try disabling plugins as well and run as bare of a Chrome as possible.
Update 2: I've disabled all plugins and extensions completely, but the problem persists. I've also let the session go on to see if it eventually recovers. After around 2 hours, it was in the same situation. No bigger CPU consumption nor memory consumption, and other Chrome instances or tabs worked perfectly fine. I was able to close the developer tools but not interact with the original page anymore.
Update 3: I've just upgraded to Chrome 41 because it has been released in the stable branch, and I know it does include a few more things in the profiling section. I tried again and it didn't seem to make any difference.
My problem may seem a bit vague (it is to me too), but here is my attempted explanation of it.
A few months ago, I implemented PDF.js in my web application. It was really useful, and I am using it for interactions with my clients.
Suddenly, last week, my clients reported to me "Aw, Snap" messages in Google Chrome on their PCs when they try to launch PDF.js. I have an iMac and two PCs at home, so I decided to test this out.
When I used Google Chrome on my iMac to launch PDF.js, I found it worked fine.
When I used Google Chrome on my first PC to launch PDF.js, I found it worked fine.
When I used Google Chrome on my second PC to launch PDF.js, even though it previously worked, it kept crashing and showing me "Aw, Snap" messages.
This was weird. I tried removing all the extensions, clearing the cache, clearing the LocalStorage, but nothing seemed to fix the problem.
I then realised, after some communication with my clients, launching PDF.js in Safari, Torch, Opera or Firefox on any operating system worked perfectly fine.
Why would this happen? I am using the web viewer in PDF.js. I also tried with the basic hello world example, but that broke as well (which I now find really weird), so I suspect there's something wrong with the rendering engine.
I also tried including the compatibility.js file after building the source, but with no avail.
Is there any known bug which causes Google Chrome tabs to crash?
Yes, I got it now.
From https://github.com/mozilla/pdf.js/issues/4104, I found the answer (thanks Rob and PDF.js dev team!). Take a look yourself!
I'm only posting this here so that anyone who stumbles upon this post with a similar problem can be helped (as this error took me quite a while to figure out).
Unfortunately, this does not seem to be the case. We've tried the latest version of pdf.js from github, also tried Chrome 33 (stable) which should have their V8 fix included and it still crashes. Also, tried the pdf.js commit mentioned in github thread (4ce6cb8 - https://github.com/mozilla/pdf.js/commit/4ce6cb8b0fa9db948516b2b738fa1503cf0ef90e) - still crashes. Also tried latest Chrome Canary available on 19/03/2014 - crash is there.
We can provide the WinDbg memory dump if it's of any help.
PS: sorry, this should be the answer to Rob W thread right above but I cannot add it there due to 0 reputation.
Hi. I have a problem with my current site that has me totally stymied.
I have implemented a javascript flipbook (like an ibook) on my website. It works in Firefox, Opera, Mac, on the iPad, etc., but not on Chrome Windows 7. In Chrome Windows 7, when I click, the page turns, and then the application resets back to the original image. In Firefox, however, it works just fine.
I have scoured the code to find the solution, troubleshooted from different angles, but can't solve the problem.
You can view the site in its current condition here : http://www.cambrianvacation.co.uk/powersb
I have only just begun working on this site, and the flipbook just has dummy content, purely for the purpose of getting it to work, so please excuse that.
If anyone can diagnose the problem, I would be very grateful.
P.S. I have only been studying Javascript for a few months, and although I have a basic understanding, it's not enough to resolve this.
It works perfectly fine for me in Windows 7 + Chrome.
Since Chrome is quite aggressive in it's caching policies, you might as well clear Chrome's cache and try again.
I have the same issue, if you go to their website over here: http://flippingbook.com/help/publisher-2/faq/launching-local-publication-in-google-chrome/ they have a guide on how to fix this issue. It is very not handy at all though because it will be fixing the problem for you only not for whoever visits your website.