faq184-3504 - Memory Management

[Neil Toulouse]

faq184-3504

I don't know if anyone uses this function, or if this issue has been reported, but my app fell over today because of it! Caused by too much RAM ;-)

Anyway easy fix, change:

DECLARE GlobalMemoryStatus IN Win32API STRING @lpMemoryStatus
lpMemoryStatus = REPLICATE(CHR(0), 32)
GlobalMemoryStatus(@lpMemoryStatus)

...to

DECLARE GlobalMemoryStatusEx IN Win32API STRING @lpMemoryStatus
lpMemoryStatus = REPLICATE(CHR(0), 32)
GlobalMemoryStatusEx(@lpMemoryStatus)

MSDN reference:

http://msdn.microsoft.com/en-us/library/aa366586(VS.85).aspx

I like work. It fascinates me. I can sit and look at it for hours...

 

[Mike Lewis]

Neil,

We use GlobalMemoryStatus() in an exercise on my advanced course. I've never known any problem with it, but, then again, I've not used it in a production environment.

Presumably, it's the SYS(3050) that's causing the problem, not the GlobalMemoryStatus().

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[Neil Toulouse]

Hi Mike!

Not sure where the problem lay (didn't look into it too much!!), but changing GlobalMemoryStatus to GlobalMemoryStatusEx did the trick!

Neil

I like work. It fascinates me. I can sit and look at it for hours...