Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. 29 Mar 2012 4:11 PM #1
    swanzoid
    swanzoid is offline
    Sencha User swanzoid's Avatar
    Join Date
    Feb 2009
    Location
    Chicago
    Posts
    1
    Vote Rating
    0
    swanzoid is on a distinguished road
      0  

    Default Ext 4.07 Charts go BOOM in Chrome 18+ on Mac

    Ext 4.07 Charts go BOOM in Chrome 18+ on Mac


    After upgrading from Chrome 17.something to Chrome 18.0.1025.142 on Mac today, I noticed at least some of the Ext JS 4.07 charts are choking the browser in a nasty way. Easy to replicate:

    When in Chrome 18+ on Mac,
    (1) go to http://dev.sencha.com/deploy/ext-4.0...harts/Pie.html
    (2) move your mouse anywhere over the chart. You'll get the Google "Aw, Snap!" blue screen of death.

    Seems to be okay in Windows though.
    Reply With Quote Reply With Quote
  2. 30 Mar 2012 5:20 AM #2
    scottmartin
    scottmartin is offline
    Sencha - Support Team scottmartin's Avatar
    Join Date
    Jul 2010
    Location
    Houston, Tx
    Posts
    7,185
    Vote Rating
    194
    scottmartin is a splendid one to behold scottmartin is a splendid one to behold scottmartin is a splendid one to behold scottmartin is a splendid one to behold scottmartin is a splendid one to behold scottmartin is a splendid one to behold scottmartin is a splendid one to behold
      0  

    Default


    Thank you for the report. This also seems to be a problem in linux as well.

    Regards,
    Scott.
    Reply With Quote Reply With Quote
  3. 5 Apr 2012 12:04 PM #3
    pierresas
    pierresas is offline
    Sencha - Ext JS Dev Team
    Join Date
    Mar 2012
    Posts
    39
    Vote Rating
    0
    pierresas is on a distinguished road
      0  

    Default


    Chrome 18.0.1025.151 was released this morning and fixes the problem. Even though the report is still under restricted access, the culprit is very likely Security issue #CVE-2011-3073 (Use-after-free in SVG resource handling).

    Update Chrome and it should work now.
    Reply With Quote Reply With Quote

Tags for this Thread