Discuss anything related to web development but no technical support questions


Post by SIM-LTD »

Does anyone has experienced the issue with google chrome browser and Scheduler (JS) or Gantt (JS) ?

Indeed, since the last version of Gooogle Chrome 75, when launching web App with Scheduler or Gantt, under a screen resolution (2880+1800 MacBook Pro) then suddenly the CPU gets crazy and the app gets frozen and cannot be used at all :x

But the odd thing is when I drag the Google Chrome browser to the external screen then the CPU consumption goes down and the web appl can be used :)

One more point this issue occurs only under Google Chrome on (MacBook Pro screen 2880+1800 ), if I run the app with SAFARI / FireFow / Opera the app goes OK.

Looking forward to reading some feedback
Attachments
Capture d’écran 2019-06-27 à 18.29.37.png
Capture d’écran 2019-06-27 à 18.29.37.png (650.26 KiB) Viewed 2589 times
Capture d’écran 2019-06-27 à 19.45.15.png
Capture d’écran 2019-06-27 à 19.45.15.png (76.4 KiB) Viewed 2589 times

Post by pmiklashevich »

Interesting report... We tried on different laptops, including 15" 2880x1800 mac pro. Worked good. It's 10-20% while loading, 50-60% while dragging a task. But when nothing happens in Gantt it's 1-2%. Could you please try open a new tab in incognito mode, close all the other tabs, and open https://bryntum.com/examples/gantt/basic/ in the incognito tab. What's the result? Also if you have an opportunity to check on another mac book with similar hardware please do. Also please try to remove your second monitor and repeat the check on your laptop. Is the result the same? Need to understand how to reproduce this.

Pavlo Miklashevych
Sr. Frontend Developer


Post by SIM-LTD »

Thank you for having taken some of your time to answer that post.
This pretty weird! And this occurs only under Google Chrome on MacBook PRO 15'', 2880x1800.

We just follow your recommendation
Remove the second Screen
and as weird the issue is, without the external (MAC Screen)
the CPU gets better (42%) the web app is now runnable not as smooth as it should be but at least it is runnable and does not freeze the browser.

We'll keep running couple investigation as per your recommendations and get back to you

Cheers

Post by SIM-LTD »

Hi There

We did run the test under incognito mode.
Nonetheless, having a web application for which we would advise our customer to run under a certain mode or browser, would have a very bad impact.
Indeed, a good web RIA (rich internet application) must be running under any type of mode and browser.

We are still facing that issue and so far we can't figure out how to handle that.
One more thing to know: the app is built with VUE CLI; It is not a classical Javascript web app.
Thus, maybe there is something with the Life Cycle Hook OR Computed properties OR Watch properties...
that should be considered... We'll let you know

Post Reply