Huuuge Memory Leak

[two_stripe]

Howdy
Superb plugin, but, it sems to have a huge memory leak

i run it on my tv (second display) while i chat, do homework and what not, and i noticed that after about half an hour the visualisations had dropped from > 45fps to under 25 fps...

i checked the winamp process and noticed that its memory usage was increasing from between 4 - 10 KB per second, and was already at 50MB by the time i checked it.

i closed the vis and memory usage dropped down to about 10 MB


when i reopend it, it again started rising at the same rate, to be at about 20MB within 10 minutes, and again running slower

has anyone else encountered this problem?

[ryan]

You sure your not running avs ? :D

Eh.. No I havent had this problem.... Rova or Krash will know whats wrong.. Sorry I cant help you.

[Rovastar]

Dispite idiots confidence I do not know what is wrong.;):D

Ummmh interesting.

I do not have a tv-out (That works properly anyway with my TV) so I cannot test what you have.

A couple of questions.

Does this happen in Windowed mode?

Does it happen when you do not use your twin veiw?

What version of MD does this happen with 1.02 or the new 1.03beta3?

Could you try these out.

Oh and post the debug file (of the problem configuration) it may show some overflow in there.

[two_stripe]

Im using MD version 1.02
Doesnt seem to make a difference if its in winamp 2.80 or winamp 3.


After testing, i have found the problem only happens when i have twin view enabled.
if twin view is enabled, it doesnt matter what device im displaying it on or if its windowed or not, it still seems to increase memory usage at about 10KB per second

No problems at all if im just using one display.


Im not sure what file you wanted me to to post here?
the md config file? or is there another one?

[two_stripe]

ahh and my video card is a GeForce 2 MX 400
with the latest drivers if that may be important

[Rovastar]

Ummh I have the same graphics card but with older drivers (so I can run DungeonSeige :) ). I think the DEt 21.83.

But no matter what drivers I use I cannot get the twinveiw to work proprly. I can get a picture but it is blurry and out of focus. But when running MD on this it does work without any memory leak.

Try downgrading your drivers. We 'may' have a small slowdown problem with the newest nVidia drivers. The jury is out for some people on this one.

OK you may as well post both the config file and the debug file. For debug tick create debug in option and get it from c:\m_debug.txt

Then try with 1.03beta3 it may (???) help.

[two_stripe]

[milkdrop debug file]
Program version is 1.02
Config.ini file is c:\program files\winamp3\plugins\milkdrop_config.ini
Preset directory is c:\program files\winamp\plugins\MilkDrop\
Parent window handle is 0038042c
MMX successfully detected.
Init: mode is FULLSCREEN
[MSG] hwnd=005204fc, msg=00000081, wParam=00000000, lParam=01d8f5a4 [WM_NCCREATE]
[MSG] hwnd=005204fc, msg=00000083, wParam=00000000, lParam=01d8f5dc [WM_NCCALCSIZE]
[MSG] hwnd=005204fc, msg=00000001, wParam=00000000, lParam=01d8f580 [WM_CREATE]
[MSG] hwnd=005204fc, msg=00000005, wParam=00000000, lParam=02580320 [WM_SIZE]
[MSG] hwnd=005204fc, msg=00000003, wParam=00000000, lParam=00000000 [WM_MOVE]
[MSG] hwnd=005204fc, msg=00000018, wParam=00000001, lParam=00000000 [WM_SHOWWINDOW]
[MSG] hwnd=005204fc, msg=00000046, wParam=00000000, lParam=01d8f5c8 [WM_WINDOWPOSCHANGING]
[MSG] hwnd=005204fc, msg=0000001c, wParam=00000001, lParam=00000000 [WM_ACTIVATEAPP]
[MSG] hwnd=005204fc, msg=00000086, wParam=00000001, lParam=002c045c [WM_NCACTIVATE]
[MSG] hwnd=005204fc, msg=00000006, wParam=00000001, lParam=002c045c [WM_ACTIVATE]
[MSG] hwnd=005204fc, msg=00000007, wParam=00450532, lParam=00000000 [WM_SETFOCUS]
WM_SETFOCUS
[MSG] hwnd=005204fc, msg=00000085, wParam=00000001, lParam=00000000 [WM_NCPAINT]
[MSG] hwnd=005204fc, msg=00000014, wParam=dd010862, lParam=00000000 [WM_ERASEBKGND]
[MSG] hwnd=005204fc, msg=00000047, wParam=00000000, lParam=01d8f5c8 [WM_WINDOWPOSCHANGED]
Init: (final) size is 800x600, final bit depth is 32
Init: Graphics window handle is 005204fc
Init: Text window handle is 00000000
Init: looking for monitor '\\.\DISPLAY2'
Init: found correct monitor
Init: creating main DirectDraw object
Init: setting cooperative level
[MSG] hwnd=005204fc, msg=00000046, wParam=00000000, lParam=01d8fc30 [WM_WINDOWPOSCHANGING]
[MSG] hwnd=005204fc, msg=00000085, wParam=00000001, lParam=00000000 [WM_NCPAINT]
[MSG] hwnd=005204fc, msg=00000014, wParam=4c010a7c, lParam=00000000 [WM_ERASEBKGND]
[MSG] hwnd=005204fc, msg=00000047, wParam=00000000, lParam=01d8fc30 [WM_WINDOWPOSCHANGED]
[MSG] hwnd=005204fc, msg=00000003, wParam=00000000, lParam=0000fce0 [WM_MOVE]
[MSG] hwnd=005204fc, msg=00000046, wParam=00000000, lParam=01d8fc30 [WM_WINDOWPOSCHANGING]
Init: setting display mode
[MSG] hwnd=005204fc, msg=00000046, wParam=00000000, lParam=01d8fa00 [WM_WINDOWPOSCHANGING]
[MSG] hwnd=005204fc, msg=00000046, wParam=00000000, lParam=01d8fa00 [WM_WINDOWPOSCHANGING]
[MSG] hwnd=005204fc, msg=0000007e, wParam=00000020, lParam=03600480 [WM_DISPLAYCHANGE]
Init: creating primary surface
Init: getting ddraw caps
Init: getting pointer to backbuffer
Init: finding D3D interface
Init: creating the D3D device
Init: getting d3d caps
Init: Caps Info: edge antialiasing for lines supported: NO
Init: Caps Info: dithering for triangles supported: YES
Init: Caps Info: max tex. size for this video card is 2048x2048
Init: Caps Info: Blending: Destcolor for Src: YES
Init: Caps Info: Blending: InvDestcolor for Src: YES
Init: Caps Info: Blending: Destcolor for Dest: YES
Init: Caps Info: Blending: InvDestcolor for Dest: YES
Init: auto-sized textures to 512x512
Init: max tex. size for this video card is 2048x2048
Init: adjusted tex. size is 512x512
Init: [re]allocating offscreen surfaces
Init: [re]allocating title surface
Init: title texture size is 512x512 (ideal size was 512x512)
Init: mesh allocation
Init: complete
[MSG] hwnd=005204fc, t=0h:00m:00.00s, msg=00000088, wParam=00000004, lParam=00000000 [WM_SYNCPAINT]
[MSG] hwnd=005204fc, t=0h:00m:00.00s, msg=00000085, wParam=00000001, lParam=00000000 [WM_NCPAINT]
[MSG] hwnd=005204fc, t=0h:00m:00.00s, msg=00000014, wParam=dd010862, lParam=00000000 [WM_ERASEBKGND]
[MSG] hwnd=005204fc, t=0h:00m:00.00s, msg=0000000f, wParam=00000000, lParam=00000000 [WM_PAINT]
-starting frame 0-
-frame 0: beginscene-
-frame 0: wbfvtv-
-frame 0: dw-
-frame 0: ds-
-frame 0: stu-
-frame 0: endscene-
-frame 0: drawUI-
-frame 0: first primary surface ~blit-
-frame 0 first blit complete-
-frame 0: exiting critical section-
-frame 0: critical section exited-
-starting frame 1-
[MSG] hwnd=005204fc, t=0h:00m:00.71s, msg=00000046, wParam=00000000, lParam=01d8fd40 [WM_WINDOWPOSCHANGING]
[MSG] hwnd=005204fc, t=0h:00m:00.71s, msg=00000047, wParam=00000000, lParam=01d8fd40 [WM_WINDOWPOSCHANGED]
[MSG] hwnd=005204fc, t=0h:00m:01.79s, msg=00000086, wParam=00000000, lParam=002c045c [WM_NCACTIVATE]
[MSG] hwnd=005204fc, t=0h:00m:06.98s, msg=00000086, wParam=00000000, lParam=00000000 [WM_NCACTIVATE]
[MSG] hwnd=005204fc, t=0h:00m:07.92s, msg=0000000f, wParam=00000000, lParam=00000000 [WM_PAINT]
[MSG] hwnd=005204fc, t=0h:00m:07.92s, msg=00000085, wParam=e9040b90, lParam=00000000 [WM_NCPAINT]
[MSG] hwnd=005204fc, t=0h:00m:07.92s, msg=00000014, wParam=370108c8, lParam=00000000 [WM_ERASEBKGND]
[MSG] hwnd=005204fc, t=0h:00m:07.92s, msg=00000088, wParam=00000004, lParam=00000000 [WM_SYNCPAINT]
[MSG] hwnd=005204fc, t=0h:00m:08.70s, msg=0000000f, wParam=00000000, lParam=00000000 [WM_PAINT]
[MSG] hwnd=005204fc, t=0h:00m:08.70s, msg=00000085, wParam=00000001, lParam=00000000 [WM_NCPAINT]
[MSG] hwnd=005204fc, t=0h:00m:08.70s, msg=00000014, wParam=370108c8, lParam=00000000 [WM_ERASEBKGND]
[MSG] hwnd=005204fc, t=0h:00m:09.01s, msg=000003e0, wParam=0073057e, lParam=c01dc01e [unknown]
fixing time gap of 0.058 seconds

[two_stripe]

uh... yuckky..... lots of stuff :P
it pretty much just repeats the last 10 lines or so over and over....

hrmm, i might try the latest beta. i dont really wanna downgrade drivers....
theres so much cool stuff with the lastest drivers which i never use lol.... or stuf i use and get sick of after 10 seconds

[Krash]

I can run my vid card to a tv, but I've never been able to get tv and monitor at the same time. I don't think I've ever had a memory leak while running MD on the tv - I've had it going for more than 12 hours straight before.
It could be milkdrop's fault, but I wouldn't be so sure.
After monitoring winamp's memory usage with mildrop running in the background, it's memory usage hovers around the 6900K mark. It goes up or down depending on the bitrate of the mp3, as far as I can tell. No indication of a leak.

Definitely try downgrading to 21.83 - I had some issues with Milkdrop when running the 28.32 drivers (the ones currently on nvidia's website). As far as I can find, there's no difference in the feature set - except possibly GeForce4 compatibility.

If I could somehow convince my vidcard to display tv and vga at the same time, I'd happily test it further.

- Krash

[two_stripe]

hrmm
well i recently formatted, and did as was suggested and installed older drivers....
i thought it was fixed
but alas... the problem remains :(