I have the same behavior as described here
with FW 184.108.40.206 on all tested G120 (custom boards)
But test programs from both mentioned threads work fine.
My app is quite memory consuming (uses about half of RAM, just about 3MByte are free).
It’s also using a couple of open Network connections (TCP/IP server and client), but it should be good under the maximum limit.
There are also a couple waiting (Manual)ResetEvent’s waiting in different threads.
In my test environment no network cable is connected.
Wenn a cable is connected (with some traffic from external source) some of the Debug.GC calls does not cause a freeze/reboot.
I can not remember that this happened with 220.127.116.11, but my project has grown since. I also thought that I did not have this problem at the beginning with 18.104.22.168, but at least my stability problems started shortly after the update.
If the GC runs on it’s own there is no freeze/reboot (happens every time when my data is initialized). No matter if I put a Debug.GC before or after that it will freeze/reboot.
This is a critical issue for me, because this should already run at a customer site.
Any hint is really appreciated.
I’ll play around with my program and the test program and will provide more info if I can find out more.
I got one more info on this.
Debug.GC freezes/reboots after allocating a lot of small objects (classes).
“A lot of” means thousands.
Allocating them is fine, using them is fine, but GC can not handle it!?
The objects are organized as a linked list (each one has a reference to the next one (but not back). I thought this would be better than an ArrayList (which causes an outofMemory exception, even that there is plenty free RAM). Can’t use a static array b/c I don’t know how many items I get when I start reading the file.