this has occurred with every amule version i've tried from 2.1.0 onwards.
in short, the longer amule is left open, the more "USER" and "GDI" objects are used. eventually the windows shell croaks and the screen becomes corrupted, window fills don't appear, menus cover the entire screen, etc., this is common behaviour when the win32 shell is starved of resources. some background information can be found
here.
whether the user/gdi object leak is occurring due to amule's code or wxwidget's code i can't say, but it definitely happens.
to reproduce:
- open task manager
- under the 'view' menu choose 'select columns'
- check 'user objects' and 'gdi objects'
- leave amule running for several hours/days
- watch as user/gdi count increases slowly but surely, jumping by a large number periodically (it's punctuated, not gradual)
- after 5 or so days (when gdi hits ~7000 or so) windows will die
this has occurred on vanilla and up-to-date installs of win2k, with 10 files being downloaded, all of which have ~1 source and so are rarely if ever generating network traffic. regardless, amule continues to increase its resource usage.
i don't know where in the amule system the leak may be occurring, but since the object counts increase in jumps periodically, i assume there's some task amule is performing every 20 minutes / 1 hour / whenever that is responsible.
whatever it is, it's a pain to have to close/reopen amule every 3-4 days just so it doesn't kill windows. i switched to amule from emuleplus because amule used around 1/4 of the memory. right now this is all i've found to complain about.
