🚀 go-pugleaf

Hi there,

I am having some problems with OS/2 2.0 lately. There seem to be some
design (!) bugs in the system which seem to eat up the free store!
An exaple:

1.  start the system editor (e.exe)
2.  select the "OPEN" menu and get the file requester
3.  enter *.argh (so that it won't find anything that fits - don't forget
    the wildcard!)
4.  keep pushing the "OPEN" button.

Now watch what is happening with your memory! After few clicks the
system has only 512 kb free store left and begins to expand the swap file.
It seems like you can fill up any partition (no matter how large) this
way :) The memory is being freed but not before I quit the application.

The same happens in every app (including mine) that uses the file
requester! Is there *any* "good" reason for this bug??? (I consider this
being a bug, of course :))

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!

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!


    adios

        Roman

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