🚀 go-pugleaf

>> Another annoyance: my program is using the PM interface, starting some
>> separate windowed and not-windowed threads... I am not using any
>> dynamic memory functions (like malloc etc.). But still, after playing
>> with it for a while, I'm getting errors like "Maximum heap size reached"!
>> (from one of the debugging hooks in my code). Sometimes the application
>> quits right after this warning. While clicking around, I keep repeating the
>> same sequences that do *not* create any new memory objects nor any new
>> items.
>> After a while, the memory status display starts showing increasingly
>> shrinking
>> store. WHY?! But sometimes the error appears even before this happens!
>> AAAAAAAAAARGH!
LS>
>> Can anybody give me a hint?! I would be *very* grateful for any help.
>> I am getting crazy here searching for a (of course still possible)
>> bug in my code and not being able to find anything wrong! HELP!
LS>
LS> Remember that there could be things going on under the covers.  For
LS> example,
LS> WinInitialize() calls DosR2StackRealloc() to increase the size of the ring
LS> 2
LS> stack (or it did in 1.x).  The memory loss (I'll leave *that* one alone)
LS> could
LS> be the result of something else you are doing.

FINALLY I have found the bug... One function in my program was calling
WinGetPS() without WinReleasePS()... My fault! This kind of bugs is quite
hard to find when code exceeds 5000 lines :)

Nevertheless, thank you for answering my mail!


    adios

        Roman

2:242/9.11@fido.org
roman_grzondziel@freax.fido.de