Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We are seeing this issue since a couple of days. Chrome (Version 45.0.2454.85 m) crashes (Aw, snap...) while displaying a Confluence page. First, the page appears to load correctly and content is being shown, but after a few seconds, Chrome crashes. The same pages show fine with IE.
Some pages are affected, while others are not - it looks pretty random to us. This may be related to Gliffy, since all of the pages showing the behavior have Gliffy diagrams. There are however pages with Gliffy diagrams showing fine.
Confluence is version 5.8.10, Gliffy is version 6.7.1. We had the same issue with Confluence 5.7 last week and were hoping to see the update resolve the issue, but no.
This is causing quite some issues here. Has anyone has seen this too? Anyone has a fix or workaround (other than using IE)?
Hi Everyone,
We are tracking this problem in the following JIRA issue: https://jira.gliffy.com/browse/GCONF-2219
This problem only affects 32-bit Chrome 45 and 46 users on Windows.
OSX users, and users of other browsers (IE, Firefox, Safari) don't seem to be affected. If you are not a Chrome 45 user on Windows and you are affected, please let us know here or via email (support@gliffy.com).
As a workaround you can use IE, Firefox, or 64-bit Chrome until this is resolved. Alternatively, if you only need to view Gliffy diagrams, you can disable the HTML5 viewer in the Gliffy Configuration page (as mentioned by another user above). We're still investigating in order to confirm that's the case.
Finally, if you have any other questions or feedback for us, please don't hesitate to send us a note: support@gliffy.com
Regards,
Mike
Gliffy, Inc.
UPDATE: The Chrome bug seems to have propagated into the upcoming 46 release, and we are still working hard on a solution. We will notify everyone here and in our JIRA issue (https://jira.gliffy.com/browse/GCONF-2219) as soon as we have a fix ready.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the information!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
UPDATE: we're still working on the problem. There are two bug filed with the Google Chromium team, located here: * https://code.google.com/p/chromium/issues/detail?id=538241 * https://code.google.com/p/chromium/issues/detail?id=523919 Unfortunately they are not accessible to the public, and have also become hidden to our developers. We will monitor the situation and keep everyone updated here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
UPDATE: it appears that Chrome 46.0.2490.80 has resolved the problem. If you are still affected then try upgrading to that version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me Chrome 46.0.2490.80 is not working. Only the first few pages...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
46.0.2490.80 m didn't resolve the problem at first but then I updated Gliffy to 6.8.0 and now it seems to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, 46.0.2490.80 m AND 6.8.0 is working for now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This was fixed when Chrome released their update: http://support.gliffy.com/entries/96400607--Aw-Snap-errors-in-the-Chrome-browser. Please see that article for further troubleshooting steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same.
Oddly, if the Chrome debug window is open (F12) before loading a page with a Gliffy diagram, then the page seems to load correctly. Timing issue?
Chrome Version 45.0.2454.85 m
Confluence 5.7.3
Gliffy 6.7.1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Malcolm, I found the same workaround. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, this temporary solution worked well. Bizarre!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
46.0.2490.33 (beta) has fixed the issue. Also agree, debugging mode on 45.0.2* works fine and you can minimize it.
Confluence: 5.8.10
Gliffy: 6.7.1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Chrome Version 45.0.2454.93 m seems to work well!
For us it works so far.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me, after update it work for one time. Entering the same space crashed the browser and even browser restart did not help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I noticed this problem as well. Chrome version 45.0.2454.85 m
Was able to resolve this issue by disabling the Google Docs extensions in Chrome and clearing the cache.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This worked for me. Chrome 45.0.2454.101 m. Confluence 5.8.8.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a user i'm hitting this problem on Chrome 45 32-bits on Windows.
As a former Chrome developer I can suggest a few things to help you report this bug to Google.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We figured out that the 64bit version of Google chrome is not affected by this issue.
You can check your version in the menu > Help and About > About Google Chrome.
We are currently using Version 45.0.2454.99 m (64-bit) with success!
When you don't have (64 bit) behind your browser you can do the following:
Hope this helps someone, if you have other findings let me know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here.
Had contact with Gliffy and they replied that it is probably a Chrome issue, but they are currently still investigating.
But there is hope! In the upcoming releases of Chrome the issue does not occur, so you could use Chrome Canary or another browser in the meantime.
For more information also see the following ticket:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To me it looks like the crash happens when Gliffy switches from the bitmap-preview to the HTML5 view. Disabling the HTML5 viewer in Gliffy's settings removes the crash - we only get the bitmaps then, which makes the page at least accessible.
So this must be something with Gliffy and Chrome. Is there anything I can provide to help analyze the root cause?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a work around ... I believe disabling the HTML5 viewer in the Gliffy settings (you need to be an administrator), will allow you to view the pages again...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This worked for all of our user base that were reporting the crashing issue on Confluence 5.8.4 with the recently updated Gliffy 6.7.1 and Chrome 45.0.2454.85 m. Great Find
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My user base report this as working if the "Disable HTML5 Viewer" is checked
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
UPDATE: Good news! We've received an update from the Chrome development team: "After two days of debugging, I'm happy to report that we have identified and fixed a crash bug that was triggered by Gliffy's code. The fix will likely ship in Chrome Canary on Monday, and will then trickle down to other channels. I'm not sure if Chrome 46 will get another update; 47 and later will definitely get the fix."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue was corrected when Chrome released their update: http://support.gliffy.com/entries/96400607--Aw-Snap-errors-in-the-Chrome-browser. Please see that article for additional troubleshooting steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is happening to me on 46.0.2490 m if I uninstall and reinstall chrome it seems to work for a while. It stopped working again for me when I activated the Gliffy plug in for Chrome. We also have the on demand gliffy that is crashing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same for 47.0.2526.21 beta-m and Gliffy 6.8.0 - currently working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, 46.0.2490.80 m AND 6.8.0 is working for now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like Chrome 46.0.2490.80 may have resolved the problem. We have tried on several different machines with that version, and non exhibit the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
An update - Chrome 47.0.2526.16 beta-m still exhibits this behaviour.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Confirming that many in my company saw the issues starting with Chrome 45.x and are still seeing it in 46.0.2490.71 m. It appears the issue only occurs (or mostly occurs?) on pages with Gliffy diagrams.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Upgraded to Gliffy 6.8.0 and the issues went away. NOTE: this is across several different Chrome versions and I did NOT need to upgrade to Chrome 46.0.2490.80 m.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Win 32, Confluence 5.6.6, Gliffy 6.7.1, Chrome Version 46.0.2490.42 beta-m still has this problem. I am able to view one or two Confluence documents with Gliffy diagrams successfully, but as soon as one crashes the page, all following attempts do the same for any document that contains a Gliffy diagram.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes you are right.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have tested the downgrade to 6.6.4 in a staging environment using Confluence 5.7 and that version doesn't seem to have conflicts with Chrome.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
same here with Confluence 5.8.9 , Gliffy 6.7.0 did not solve it, 6.6.4 did
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same issue here.
Confluence 5.8.10
Gliffy 6.7.1
Chrome 45.0.2454.85m
As it seems the issue also affects 6.7.0, has anyone tried downgrading Gliffy to 6.6.4?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.