http://hem.bredband.net/b247083/temp/Untitled-1.jpg
--------------------------
Ill tell you what's wrong. Its too big to be posted inline!
The Image Has Been Linked
// Seph
http://hem.bredband.net/b247083/temp/Untitled-1.jpg
--------------------------
Ill tell you what's wrong. Its too big to be posted inline!
The Image Has Been Linked
// Seph
120 MB for AveDesk is really wrong.
At first glance I won't blame that on AveDesk but on a Desklet.
Please help us find out:
Backup your Theme.ini elsewhere and remove your desklets by type,
using the following drill:
Remove all SysStat, save configuration, restart AveDesk, measure mem usage.
Remove all Folder, save configuration, restart AveDesk, measure mem usage.
Remove all Drive, save configuration, restart AveDesk, measure mem usage.
Close AveDesk, restore original Theme.ini, restart.
Post the mem usage here when done.
Thanks,
herd
PS: Shmengie, LoofyGun - I removed your posts because of being pointless.
All other posts saying 'But mine uses 7.0 MB only' or 'wow' shall be removed
without further notice - please help us getting this fixed ASAP.
Originally posted by herd@Aug 28 2004, 10:58 PM120 MB for AveDesk is really wrong.
At first glance I won't blame that on AveDesk but on a Desklet.
Please help us find out:
Backup your Theme.ini elsewhere and remove your desklets by type,
using the following drill:
Remove all SysStat, save configuration, restart AveDesk, measure mem usage.
Remove all Folder, save configuration, restart AveDesk, measure mem usage.
Remove all Drive, save configuration, restart AveDesk, measure mem usage.
Close AveDesk, restore original Theme.ini, restart.
Post the mem usage here when done.
Thanks,
herd
PS: Shmengie, LoofyGun - I removed your posts because of being pointless.
All other posts saying 'But mine uses 7.0 MB only' or 'wow' shall be removed
without further notice - please help us getting this fixed ASAP.
<{POST_SNAPBACK}>
The thing is.. at startup with my current configuration avedesk uses around 5000 kb.. and after maybe 24 hours of usuage it's has increased tremendously to 120000 kb.. so I suppose there's a memory leak somewhere...
I'll post my experiences here for you to look at.
Avedesk with current configuration as in the picture @ startup (29th august, 00:50am GMT+1): 4764 kb
I dont see an iTunes widget in use there, but I have to ask - are you using one and turning it on/ off? There was a confirmed memory issue with a previous iTunes desklet release.
Originally posted by deadzombie@Aug 29 2004, 12:55 AMI dont see an iTunes widget in use there, but I have to ask - are you using one and turning it on/ off? There was a confirmed memory issue with a previous iTunes desklet release.
<{POST_SNAPBACK}>
Turning something on and off.. not that I know off.. One thing that I use is the "switchable weather widget" the one that uses a VB script to switch from small-medium-big.
There seems to be the following issue with SysStats:
Whenever a config is loaded, parts of the previous config remain
in memory. Judge is working on that AFAIK.
I'd like a volunteer to confirm this, so that Judge gets to know.
herd, I think that situation is most apparent when loading an analog clock and subsequently (using the same instance of SysStats) loading a digital clock. What would happen is that the digital display moves around like the hands of the analog clock.
Originally posted by herd@Aug 29 2004, 10:58 AMThere seems to be the following issue with SysStats:
Whenever a config is loaded, parts of the previous config remain
in memory. Judge is working on that AFAIK.
I'd like a volunteer to confirm this, so that Judge gets to know.
<{POST_SNAPBACK}>
That still shouldn't cause 120MB of memory usage, though...
Update: Since my last post the mem usuage has been at 5000 kb stable... maybe it just was a random memory leak.. but still it's not good...
I remember that after noticing the huge mem amount it took up I moved my pagefile from e: to c: and let windows adjust it automatically to see if it would be any improvement... I don't know if this is the result of it though...
Originally posted by pcw@Aug 30 2004, 10:16 PMUpdate: Since my last post the mem usuage has been at 5000 kb stable... maybe it just was a random memory leak.. but still it's not good...
I remember that after noticing the huge mem amount it took up I moved my pagefile from e: to c: and let windows adjust it automatically to see if it would be any improvement... I don't know if this is the result of it though...
<{POST_SNAPBACK}>
OK, go to the processes view in task manager again and click view/columns.
Add the column that shows total paged memory - maybe AveDesk has paged
all its or its desklets leaked memory to the page file...
PS: since I have only localized windows, I can't 100% translate the column to
check - it could be 'Virtual memory size'. It's the second from the top of the
rightmost batch.
Originally posted by herd@Aug 30 2004, 10:39 PMOK, go to the processes view in task manager again and click view/columns.
Add the column that shows total paged memory - maybe AveDesk has paged
all its or its desklets leaked memory to the page file...
PS: since I have only localized windows, I can't 100% translate the column to
check - it could be 'Virtual memory size'. It's the second from the top of the
rightmost batch.
<{POST_SNAPBACK}>
Holy crap! Didn't even think of that...
I added the Virtual Memory column to the task manager.. and it shows mem usuage Avedesk 5000kb and Virtual memory usuage for Avedesk 138000 kb!
I always wondered why my pagefile recently have grown to be so huge....
Unfortunately, there is no way to measure which DLL has allocated so much
RAM without turning AveDesk into a debugger of itself...
I'd like to ask you to perform the drill I mentioned above while monitoring
the paged memory, too. Another good idea would be to check the mark of
'handle count' and look if it rises with the memory leakage, perhaps some
files aren't closed which need checking at regular intervals or internet lookups
(this weather config frightens me) that fail are handled leakily...
(I think I should add a memory monitor for AD 1.2)
hth,
herd
Originally posted by herd@Aug 31 2004, 01:09 AMUnfortunately, there is no way to measure which DLL has allocated so much
RAM without turning AveDesk into a debugger of itself...
I'd like to ask you to perform the drill I mentioned above while monitoring
the paged memory, too. Another good idea would be to check the mark of
'handle count' and look if it rises with the memory leakage, perhaps some
files aren't closed which need checking at regular intervals or internet lookups
(this weather config frightens me) that fail are handled leakily...
(I think I should add a memory monitor for AD 1.2)
hth,
herd
<{POST_SNAPBACK}>
Now the VM size of Avedesk has risen to 190000 kb... handle count is 420..
I'll try the drill you told me about...
I forgot to remove the Sysstats and noticed now today that the VM size has risen from 190000 kb to 250000kb...
I'll begin now with removing the weatherconfig ( boohoo
) and keep monitoring it...
I have the same memory problem with Dashclock for sysstats in ObjectDock.
Posts Removed.
As noted by herd, all "it only uses x for me" posts are worthless, and will be removed.
Ergo: Don't bother posting if that's all you've got to say!
-----------------------
Stevie BM