This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WebAdmin memory leak?

There seems to be a direct relationship between how long a web admin session lasts and a slow build in memory usage. I frequently leave the dashboard open for long periods of time and I've noticed that the system memory usage slowly builds over the hours. If I close the page for a while, like 10 or 15 minutes, and log in again the usage will have dropped dramatically but it slowly starts building up again. Can anyone else replicate this?

I did search before posting this and I didn't find any similar reports. Also not sure if this is the right place for this; sorry.

This thread was automatically locked due to age.

0 BAlfson over 14 years ago

From the command line, you can run top, then touch m to see the processes listed in order of memory usage. It would be interesting to compare before and after closing/restarting WebAdmin to see which process is responsible. Also, please note precise version number.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 Jack Daniel over 14 years ago in reply to BAlfson

We have had a few reports of this, and the QA team is aware of the issue. Soong, could you please provide the software version number you are currently running?

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 Kingbuzzo over 14 years ago

I have experienced this issue as well with IE7 (XP), IE8 (Vista), & IE8 (W7)...

7.5x
Cancel
Vote Up 0 Vote Down

Cancel
0 Soong over 14 years ago in reply to Jack Daniel

From the command line, you can run top, then touch m to see the processes listed in order of memory usage. It would be interesting to compare before and after closing/restarting WebAdmin to see which process is responsible. Also, please note precise version number.

Cheers - Bob
I got screen captures of the top list as well as the Reporting > Hardware graphs and I just opened a WebAdmin session. I'll do the same at the end of my shift and post the results back here.
We have had a few reports of this, and the QA team is aware of the issue. Soong, could you please provide the software version number you are currently running?

Thanks
Currently running 8.002. I'm not 100% sure but the problem may have existed when I was running 7.507. I just upgraded over the weekend going from 7.507 to 8.002 as well as going from one to two gigabytes of ram. I upgraded the ram because usage would frequently get high enough that it would start using the swap. But to be clear I didn't notice the correlation between leaving the WebAdmin open and the memory usage until I upgraded to v8.
Cancel
Vote Up 0 Vote Down

Cancel
0 Soong over 14 years ago in reply to Soong

The memory usage did grow steadily; up about 16 percent (~375MB) . I navigated to the "Reporting > Hardware" graphs and the memory usage plummeted shortly thereafter. It would seem the memory problem is related to the dashboard, or at least it seems it's not related to the "Reporting > Hardware" page.

The process taking all the memory was one of the wwwrun / wwwrun / index.plx ones but I didn't get the process ID before the usage dropped.

I'll repeat the experiment overnight.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 14 years ago

Soong, I think that Jack's comment means that they already have the information that I hoped you would discover. In any case, I was suggesting that you log in to the command line with PuTTy or SSH and run the command top, then touch m to see the memory in use. Then, start WebAdmin from your browser and leave it on the Dashboard.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 Billybob over 14 years ago in reply to Soong

The process taking all the memory was one of the wwwrun / wwwrun / index.plx ones but I didn't get the process ID before the usage dropped.

I'll repeat the experiment overnight.

Webadmin is index.plx process and it consumes a significant amount of ram when running. Interestingly, it doesn't die instantly when you log out of webadmin. I personally have never had the problem with memory leak even with leaving the webadmin dashboard window running for 24 hours with refresh set to 5 seconds.

I am glad the developers have an idea of what is going on though for cases where it is a problem.
Cancel
Vote Up 0 Vote Down

Cancel
0 RFCat_vk_01 over 14 years ago in reply to Billybob

I am glad it has finally been recognised.
I could make it happen on 3 different type of ASGs with different version of software.

This issue was raised during the V8B, but was not repeatable by the developers.

Regards

Ian M
Cancel
Vote Up 0 Vote Down

Cancel
0 Soong over 14 years ago in reply to RFCat_vk_01

top sorted by memory consumption prior to logging into the WebAdmin dashboard:
http://nothingunreal.com/dump/astaromem/0top0.png
and sorted by process id (to see the whole list if needed:
http://nothingunreal.com/dump/astaromem/0top1.png
http://nothingunreal.com/dump/astaromem/0top2.png

Immediately after starting the Web Admin session:
http://nothingunreal.com/dump/astaromem/1dash0.png
http://nothingunreal.com/dump/astaromem/1top3.png
the whole list:
http://nothingunreal.com/dump/astaromem/1top4.png
http://nothingunreal.com/dump/astaromem/1top5.png

13(?) hours later:
http://nothingunreal.com/dump/astaromem/2dash1.png
http://nothingunreal.com/dump/astaromem/2hardware0.png
http://nothingunreal.com/dump/astaromem/2top6.png
the whole list:
http://nothingunreal.com/dump/astaromem/2top7.png
http://nothingunreal.com/dump/astaromem/2top8.png
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 14 years ago

Hmmm, wwwrun is the culprit. Toggling the HTTP/S Proxy off then on probably would not affect that because it's part of the server software running WebAdmin.

Good work, Soong, that should be all the information Astaro needs.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel