BUG: Nonpaged pool leak

Hi!
Sounds strange, but WinUAE 1.4.2, and recent betas causes non paged pool leakage while sound card initialization on start, about 300k per launch, and not returned on exit. Turning sound emulation off fixes that.
Before that, I used WinUAE1.3.4 and previous, those are not affected.

When I upgraded and used old configs, there were instant nonpaged pool exhaustion due to empty "sound device" field.

Verified on w2k sp4 and w2003 sp2.

[Toni Wilen]

You forgot important information like used sound card and driver (make sure it is latest)

1.4.1+ updated to latest DirectSound libraries (previous was DX8 level libs), there is no other changes (except if using 4+ channel modes).

Driver bug most likely, especially if it causes bluescreen (I presume nonpaged pool leak = bluescreen message?)

Audigy4 with latest kX driver http://www.kxproject.com, http://www.driverheaven.net/forumdisplay.php?f=74

I omited info because older winuae wasn't trigger that. Now I'll check with older kX and creative's ones, thank you.

Nonpaged pool leak is an ordinary leak. Just very bad behaviour... You may use poolmon from reskit to look tags of allocations. Tag of interest is MmCm which belongs to ntoskrnl.exe itself.

[Toni Wilen]

WinUAE only allocates one sound buffer (which is reallocated if sound configuration changes), non-playing part is continuously updated on the fly (lock, update, unlock)

I am still 99.9% sure it is a driver bug.

Yes-yes. You're right! Only one thing I can't understand, how hundreds of other apps working without that behaviour.

Going to post that on kX forum 8\

Thank you