Forum Home › Forums › Development and Integration › Firefox left w/ graphs open overtakes RAM
- This topic has 16 replies, 3 voices, and was last updated 7 years, 11 months ago by Mikhail.
-
AuthorPosts
-
April 27, 2016 at 9:40 am #1026inpelsaParticipant
Hi!
If I leave Firefox open with a channel graph open, the next day Firefox is taking 2 Gb RAM and at the end Firefox crashes.
Is there any known memory leakage that could make this?
I will give a try to IE and Chome on other computers…
thanks!
April 27, 2016 at 1:20 pm #1030MikhailModeratorHi,
Is the only chart web page is open? I mean do you close the main web form with scheme or table view?When you test the same with IE and Chrome please write about the result.
April 27, 2016 at 1:24 pm #1031MikhailModeratorIs there any known memory leakage that could make this?
Chart component uses JavaScript and web service. JavaScript has auto memory management and should work correctly. Let’s compare with other browsers. Close all other pages except chart.
April 27, 2016 at 2:58 pm #1034inpelsaParticipantAfter +- 15 minutes running:
– 2 computers, Win7 64 bit
– Each web explorer with 2 tabs: table view + 1 channel graphResults on both computers:
– IE 9.0.8112 x64 3 min CPU 660 MB RAM (100 MB at the beginning)
– Firefox 45 2 min CPU 395 MB RAM (120 MB at the beginning)
– Chrome 49.0 40 secs CPU 25 MB RAM (same memory at the beginning) (on the 2nd computer it took 300 MB RAM)On all cases, seems that closing/not opening Table View tab solves the problem but… I need it.
I think it’s clear… 🙂
PD: Javascript will dispose/collect garbage/free memory if objects/data are not referenced any more (or marked for dispose…) in any means.
April 27, 2016 at 4:25 pm #1042MikhailModeratorPeriodically I do similar tests. I should repeat them.
That’s funny, but a few years ago SCADA-Web run stable on IE for days. And Chrome supported Silverlight 🙂
I think that the cause of memory leak is reloading frames within web page. This approach is outdated and will be changed to REST API.April 27, 2016 at 5:04 pm #1044inpelsaParticipantTechnology never stops 🙂
Maybe related to jQuery: https://github.com/jquery/jquery/issues/2685
Through reloading/closing full Table View tab doesn’t release memory on Firefox :/
If you find a fix while you finish the new API drop me a line please, is a bit anonying restarting web browser every few hours.April 28, 2016 at 6:28 am #1051MikhailModeratorMy results for the current version of SCADA-Web after 1 or 2 hours of work:
FF – changed: 1.2GB => 400 MB => 600MB => 20MB – freeze
IE – increased to 600MB – freeze
Edge – changed: 15MB => 3MB, but background Edge process 2GB
Chrome – changed: 25MB => 15MB, but background Chrome process eats RAM, sometimes page can’t be displayed and memory is cleared – not fairI will try with old jQuery. The jQuery ticket that you found is very interesting.
New scheme engine after the night:
FF – 130MB
Chrome – 17MB + 21MB background Chrome processApril 28, 2016 at 11:10 am #1054inpelsaParticipantNew scheme looks quite good!
Let me know when/where I can download that version!
April 28, 2016 at 11:25 am #1056MikhailModeratorOf course. I do the best to make this moment closer.
April 28, 2016 at 11:37 am #1057inpelsaParticipantBy the way… there is also something anonying on the table view, if for any reason columns are too wide (numbers with values of ~4 billions) there is no horizontal scroll bar to see columns to the right.
Even if I choose 0-11h I can only see 0-8 with a 22″ monitor.
this has a low priority 🙂
April 28, 2016 at 5:39 pm #1062MikhailModeratorHm, scrollbar used to be, but disappeared )
May 12, 2016 at 7:20 pm #1132Washu HakubiParticipantHad the same scroll bar problem today.
To make the horizontal bar appear, on the tableView.css in the line number 8 set overflow to auto.
The horizontal bar will appear right above the event line.Before:
#divTableView { overflow: hidden; }
After:
#divTableView { overflow: auto; }
May 13, 2016 at 12:12 pm #1147inpelsaParticipantPerfect!!
May 23, 2016 at 5:05 pm #1229inpelsaParticipantMikhail, did you find the bug about memory usage?
May 24, 2016 at 5:49 am #1231MikhailModeratorNo, I think it’s better to release the new web app ASAP.
-
AuthorPosts
- You must be logged in to reply to this topic.