Home forums Report Bugs A webpage is slowing down your browser – Firefox Hang – Specific Date

This topic contains 4 replies, has 2 voices, and was last updated by  acro_prop 3 months, 3 weeks ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #19755

    acro_prop
    Member

    If you run the following with specific dates of Date(2018, 02, 24… this code works as expected in jsfiddle etc.

    However, if you attempt to run it as-below with the date Date(2018, 02, 25… – then it causes the Firefox browser to totally choke across all platforms.

    
    var chart = new CanvasJS.Chart("chartContainer",
        {
          zoomEnabled: true,
          panEnabled: true,
          title:{ text: "Latest data" },
          data: [
          {
            showInLegend: true,
            lineThickness: 1,
    	color: "#6633FF",
            type: "line",
            name: "Load",
            dataPoints: [
     { x: new Date(2018, 02, 25, 00, 00, 06, 0), y: 1.000 },
     { x: new Date(2018, 02, 25, 02, 28, 22, 0), y: 2.000 },
            ]
          },
          ]
        });
        chart.render();
    

    I tried to debug the issue a little – but ran out of time. The exact error message is “(firefox banner) A webpage is slowing down your browser, what would you like to do? Close / Wait”. After this error manifests, Firefox is misbehaving. Tried various FF versions on Win & Lin. Please help! Many Thanks in advance.

    P.S. Bug does not appear in Opera/Windows.

    • This topic was modified 3 months, 3 weeks ago by  acro_prop. Reason: additional information specified
    #19757

    Vishwas R
    Keymaster

    @acro_prop,

    The code you have shared seems to be working fine across all browsers including Firefox across different platforms. Can you kindly share the code either as html file (either over Google-Drive or Onedrive) or create jsfiddle reproducing the issue so that we can understand your scenario better and help you out?


    Vishwas R
    Team CanvasJS

    #19764

    acro_prop
    Member

    First thing this morning, I opened the page that first displayed the symptoms. The page worked. Bug gone. No changes at all. But that made me even more curious and just more than a bit scared.

    So I opened Windows 7, FF, and jsfiddle, and then ran that code and the bug was once more visible. Hang on Linux, “Gah. Your tab just crashed.” on Win 7 Latest Firefox ESR.

    Jsfiddle url is : JsFiddle showing faulty code it is literally the above code cut and pasted. All are x86_64 arch, all Firefoxes are ESR’s.

    I will investigate a bit more and let you know. Perhaps it is an interaction with builtin pdf-viewer/youtube/plugin or something I will let you know if I discover root cause. Many Thanks.

    #19777

    Vishwas R
    Keymaster

    @acro_prop,

    We are unable to find any issue when the chart related code is executed separately either in jsfiddle or in html file. Can you kindly check the plugins that are being used in your application, which may be causing the issue?


    Vishwas R
    Team CanvasJS

    #19784

    acro_prop
    Member

    Ok. Reproduce this bug by using the JSfiddle linked above, on any Firefox earlier than current releas(es).

    All the Firefox Extended Release versions (ESR’s) crash on it – even in Safe Mode (with all plugins disabled) – seemingly across all platforms. Early FF versions like 46.0.1 32 bit crash across the board on it in safe mode faithfully the older FF’s modal dialog box outline the exception with line numbers which differ each time (canvas.min.js:10/71/82)…

    Jsfiddle will not allow debugging ‘…is a blackbox…’ message; although some meaning may be derived from the jsfiddle stack trace by somebody with experience of the inners – but I can’t export it.

    Debian LiveCD Firefox 58.0.2 is OK, and thankfully does not wear the Quantum interface. I guess I am going to have to bite it and dump either firefox or canvasjs – sucks to be me.

    Summary : Firefox releases earlier than Late 2017 / Early 2018 do not reliably support canvasjs in all scenarios, most likely to bugs in the javascript implimentation.

    Many Thanks for your support throughout.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.