Chrome browser crashes ("Aw Snap!") randomly when rendering Ext JS Donut Charts.
I initially thought this was a data issue. But, I was able to reproduce it even on Ext JS Kitchen sink (http://examples.sencha.com/extjs/6.0.2/examples/kitchensink/?charts=true#pie-donut)
To reproduce this just check and un-check the boxes on Legend below the donut chart. which will cause the chart to re-render and eventually crash (it sometimes takes me 20,30+ clicks to reproduce this).
This issue is limited to Chrome Browser only.
I've found few threads describing the same issue
Link1
Link2
But, No solution yet.
I need help finding a workaround or solution.
Thanks in advance.
This is known Chrome issue. Should be fixed with Chrome 55 which was released couple of days ago.
You can see the Chromium ticket here: https://bugs.chromium.org/p/chromium/issues/detail?id=666046
Testing: I have app which uses Ext 6.2 charts interactions a lot. It used to crash in couple of seconds - with version 55 so far no crash! :)
Related
Good morning,
I'm working on implementing a Telerik RadGrid for my company, but have found it difficult to optimize the grid to work efficiently on IE; some of our clients primarily uses an older version (v.7) of that specific browser.
The use case is one such as the user will be able to specify the group (either Red or Green) and then a type (the Red grid has ~20 different types, the Green has one).
The issue I'm facing is that the Green grid takes nearly 9 seconds to load on IE.
These are the loadtimes on different browsers:
Chrome, Firefox: 4 seconds to load (which is acceptable, but not good).
Edge: 6 secounds
IE (latest version): 8.6 seconds.
I've already checked the view that both the grids use to get its data from and it loads in less than a second, so that wouldn't be a problem.
I'm assuming it could be something with the client side operations (hiding / displaying columns, enabling/disabling buttons, setting column's datafields etc).
The reason I am posting this is to see if there are any potential bottlenecks that all of you might have noticed while either working with RadGrid / GridView etc.
I'm not really sure what code might be relevant for this issue, so if you need any snippets etc, I'd happily get it on request.
Thanks for your consideration.
Regards,
Joakim
I am trying to build a map-based web app using mapbox and leaflet.js.
I am loading around 300 markers into a featureLayer from a geoJSON file. This seems to work beautifully in every browser except internet explorer, which freezes for a good 10 seconds or so every time markers are loaded or filtered using featureLayer.setFilter. I have uploaded a demo of this here.
Locking at the IE performance analysis the culprit seems to be the 'addDoubleTapListener'. This seems to be a known issue (https://github.com/Leaflet/Leaflet/issues/4357), and the solutions suggest rolling back to leaflet 0.7.5, or using the 0.7.7.1 branch (which has a fix that reverts touch detection). I have tried both, and neither seem to have any effect on the issue. Upgrading to the leaflet 1.0.0-beta is also suggested, but this doesn't seem to be compatible with the current mapbox...
Any help with overcoming this issue would be much appreciated.
Ok the solution I found was to remove the following lines from leaflet-src.js 0.7.7.1:
if (L.Browser.touch && (type === 'dblclick') && this.addDoubleTapListener) {
this.addDoubleTapListener(obj, handler, id);
}
IE now loads the markers lightning fast and all of the functions appear to still be working in all the devices I tried. Not an ideal solution, but will serve as a stop-gap solution until Mapbox supports Leaflet 1.0.0.
I've been working on an HTML5 game for close to a year now, and the newest version of Chrome (49) has completely wrecked its performance. The game that was easily running at 60FPS now struggles to get over 5-10 after updating Chrome. I've verified that it is the Chrome update using a stable version of the game and updating Chrome on my gaming PC, to see the same drop in performance.
I figured there would be something on the web or from Google about this by now, has anyone else seen this hit in performance? Is anyone aware of what has changed in Chrome that may have caused this issue?
I did notice performance issues when calling drawImage() (about 10k sprites). The issue seems to be fixed in chrome 53, so I think it was a performance regression.
I am using pdf.js in my web application and it works fine until I updated chrome to Version 30.0.1599.69 m this morning.
The PDF is rendered with wrong character. Zooming in or out may correct the character but it doesn't work to all document. Different document may be 'corrected' with different zoom scale.
Sometime zooming doesn't fix the problem.
Does anyone facing the same problem? Any solution?
Screen capture:
Temporary solution is to fix users' chrome version to version 29. This is the most practical solution in our case for the time being.
I coded some d3.j code that is svg visualization library and in my Mint installation firefox is really bad for rendering it. Is it about my installation or is it the general case?
Here is a example link for d3.js example
Almost 2 years later, and the animation in FF is still a problem with FF29. It's a shame.
I had the same problem. Transitions are very slow in FF 15 compared to Chrome and Safari. But you should try FF beta or Aurora. They come with significant performance improvements for SVG transitions and d3.js. My transitions are now running smoothly.