Memory locked from allocation

[Phi]

Yo,
When running MMF2, with most projects I am unable to work. I screen-recorded demonstrating MMF2's involvement and PM'd the admins several weeks ago. To their credit, they have been a lot more informative and quick to respond then other admins I've had dealings with.

The menus and dialogs just plain don't load. To quote an error message I'm getting while running MMF2 and attempting to delete a file in Windows Explorer:

---------------------------
Error Deleting File or Folder
---------------------------
Cannot delete Trix: There is not enough free memory.

Quit one or more programs, and then try again.
---------------------------
OK   
---------------------------

MMF2 refuses to load menus, and won't build applications, and eventually closes itself.

In the video, you can see I still have several gigabytes of memory left, but when I run MMF2, the entire system goes berserk. Some programs even start closing for protection, like Visual Studio, and others are so drained of memory they can't do anything simple, like browsing to a different folder in Windows Explorer usually messes up all the toolbars on the window, and sometimes it just cancels the browse command and does nothing.

The issue is directly involved with either MMF2 or some extensions. Before I start debugging by process of elimination with extensions, as it's obvious the system doesn't understand how much memory is actually free, I'd like to know if there's anything that you can forget to release with the OS which won't show on the memory meter, but still use up a lot of memory (maybe handles, using the wrong combination of malloc/new/GlobalAlloc/LocalAlloc with their respective release functions). Running out of memory in such an extreme way is so rare that even doing a web search doesn't reveal much of value.

This bug is stopping me working with just about any project in MMF2 right now, including several paid ones and free CT community ones, so I'd appreciate any help I can get - although I would go ahead with releasing any new builds as apparently I'm the only one getting the bug (or the only one getting it to such a noticeable extent).

Thanks, Φ

[LB]

Do you think it could be related to one of the extensions being loaded?

[Phi]

That's more than likely as this bug hasn't been reported before.

System specs for the lulz:

Motherboard: MSI-7680 with automatic overclocking system OC Genie ftw!
Processor: Intel Core i5 2500k, quad-core
Memory: 6GB, although only 3.2GB can be accessed because
OS: Windows XP 32-bit
Display card: (built-in) HD Graphics 3000
VRAM: 0mb (uses regular RAM, 256mb)

I'm assuming that it does have something to do with the extensions, so I'm using process of elimination. The problem is intermittent, which doesn't help.

[Phi]

On a related note, I did some debugging with WinDBG, and found there's 27 handles which aren't freed between Create New Object list refreshes.

0:010> !htrace -diff
Handle tracing information snapshot successfully taken.
0x1000 new stack traces since the previous snapshot.
Ignoring handles that were already closed...
Outstanding handles opened since the previous snapshot:
--------------------------------------
Handle = 0x00000e90 - OPEN
Thread ID = 0x00000984, Process ID = 0x00000aa8

0x7c801da8: kernel32!LoadLibraryA+0x0000002d
0x004f8a74: MMF2+0x000f8a74
0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d8c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x7c91e2be: ntdll!CsrAllocateMessagePointer+0x00000cbd
0x7c91d980: ntdll!CsrAllocateMessagePointer+0x0000037f
0x7c91d73b: ntdll!CsrAllocateMessagePointer+0x0000013a
0x7c915b0a: ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x0000020f
0x7c91c209: ntdll!LdrQueryImageFileExecutionOptions+0x00000486
0x7c91c3cd: ntdll!LdrQueryImageFileExecutionOptions+0x0000064a
0x7c91c374: ntdll!LdrQueryImageFileExecutionOptions+0x000005f1
0x7c91b2c6: ntdll!snwprintf+0x00000604
0x7c91c89e: ntdll!LdrDisableThreadCalloutsForDll+0x000000ec
--------------------------------------
Handle = 0x00000be4 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x7c80ea2b: kernel32!CreateMutexA+0x0000004c
0x02311a3a: +0x02311a3a
0x023119da: +0x023119da
0x02311566: +0x02311566
0x0231111b: +0x0231111b
0x023110ff: +0x023110ff
0x02311072: +0x02311072
0x7c90118a: ntdll!LdrInitializeThunk+0x00000024
0x7c91b5d2: ntdll!LdrFindResourceDirectory_U+0x0000028d
0x7c9162db: ntdll!RtlValidateUnicodeString+0x00000511
0x7c91643d: ntdll!LdrLoadDll+0x00000110
--------------------------------------
Handle = 0x000008b4 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x000008b0 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x000008ac - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000868 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x0000085c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000704 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000814 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x0000081c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000ffc - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000fb8 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000fb4 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000fac - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000f68 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000f64 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000f3c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000f1c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000f18 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000f14 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000ed0 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000ecc - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x7c91643d: ntdll!LdrLoadDll+0x00000110
0x7c801bbd: kernel32!LoadLibraryExW+0x000000c8
0x7c801d72: kernel32!LoadLibraryExA+0x0000001f
0x7c801da8: kernel32!LoadLibraryA+0x0000002d
--------------------------------------
Handle = 0x00000ec8 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x7c90118a: ntdll!LdrInitializeThunk+0x00000024
0x7c91b5d2: ntdll!LdrFindResourceDirectory_U+0x0000028d
0x7c9162db: ntdll!RtlValidateUnicodeString+0x00000511
0x7c91643d: ntdll!LdrLoadDll+0x00000110
--------------------------------------
Handle = 0x00000e8c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000e88 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000e84 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000e3c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000e38 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000e34 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000dc8 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000dc4 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Handle = 0x00000dc0 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d7c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d74 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x7c801da8: kernel32!LoadLibraryA+0x0000002d
0x004f8a74: MMF2+0x000f8a74
0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d78 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d30 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d2c - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

0x004f8a74: MMF2+0x000f8a74
0x0052a260: MMF2+0x0012a260
0x0055d85f: MMF2+0x0015d85f
--------------------------------------
Handle = 0x00000d28 - OPEN
Thread ID = 0x00000a4c, Process ID = 0x00000aa8

--------------------------------------
Displayed 0x27 stack traces for outstanding handles opened since the previous snapshot.

So it's leaking handles, at least.