If you have all those things and NOT ethernet yet, and you’re running out of memory on an EMX, then you have a code problem for sure. Something isn’t being cleaned up when it should. Forcing GC may be necessary occasionally but in most cases watching what is changing in your memory is the best indicator of what you need to track down.
Thanks for the replies. Yes indeed my biggest issue was indeed a bug in my code - as I also expected ;-)). I was leaving some ‘messages’ on a queue because I had disable the Ethernet port temporarily :-((.
The GC debug prints however do appear to change at times (hence my concern), but they have remained pretty stable since fixing this bug.
I am still however disappointed that MS decided to remove code which would allow the heap to be walked (DumpHeap) :-((. That would have told me immediately what was being left in memory :-((.