You must be logged in to post your query.
Home › Forums › Chart Support › firefox report canvasjs slow down browser when render live data chart
Tagged: firefox 67.0.1 (64-bit) windows
Seeing following error when load it on firefox browser, can you help to see what could be wrong? my canvasjs version is v2.2 GA
Error: Script terminated by timeout at: la.prototype._getLineWithWidth@https://10.3.17.171/custom/nmsweb/lib/canvas/canvasjs.min.js:99:84 la.prototype._wrapText@https://10.3.17.171/custom/nmsweb/lib/canvas/canvasjs.min.js:100:177 la.prototype.measureText@https://10.3.17.171/custom/nmsweb/lib/canvas/canvasjs.min.js:98:348 Ka.Chart</r.prototype.renderIndexLabels@https://10.3.17.171/custom/nmsweb/lib/canvas/canvasjs.min.js:264:83 Ka.Chart</r.prototype.render@https://10.3.17.171/custom/nmsweb/lib/canvas/canvasjs.min.js:190:435
Here is firefox browser version for you reference 67.0.1 (64-bit) windows
@ljohnson,
Can you kindly share JSFiddle reproducing the issue you are facing so that we can look into the code, understand the scenario better and help you out?
— Vishwas R Team CanvasJS
I don’t have a JSFiddle to reproducing the issue since the live data is from server dynamically generated. Can you tell what the error is? and is there a way to handle such timeout?
We are unable to reproduce the issue at our end. I request you to share a sample reproducing the issue – along with sample data so that we can look into the code, understand the scenario better and help you resolve the same.
I would also recommend you to use the latest version of CanvasJS and try the same.
Thanks Vishwas. I tried version v2.3.1 GA, no longer seeing the timeout error. Still, I want to understand what could be wrong, Can you tell if v2.3.1 handles such case differently from v2.2?
In v2.3GA, we have improved resource handling in case of dynamic / live charts which reduces memory consumption. However we are not sure about your use-case and unable to reproduce the issue you are mentioning with v2.2 aswell. If you could share us the use-case over JSFiddle or in a static HTML file, we can investigate further, brief more about the exact issue (and fix if any).
You must be logged in to reply to this topic. Login/Register