Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Global Discussion > System.gc() and memory management

System.gc() and memory management | Telit Cinterion IoT Developer Community

Like
0
1
relihanl's picture
relihanl

March 31, 2014 - 9:35pm, 3536 views

Hi... can anyone tell me how System.gc() is implemented for the EGS5, etc. When I issue this command, can I be sure that all garbage is collected? I'm suspicious as it seems to execute very quickly. Also, what should happen when I run out of memory? In my application when free memory gets to about 112K, some of my threads terminate with no warning or Java exception. L
1
Comment
Log in or register to post comments
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Apr 1 2014 - 4:36pm
Hi Liam, System.gc only notifies JVM to run garbage collector, but does not guarantee that it will happen, so you can't be 100% sure that gc is invoked at the time. Regarding out of memory issue: according to Java API reference OutOfMemoryError is "thrown when the Java Virtual Machine cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector." So you have guaranteed that the gc will try to free the memory before throwing an exception. If the exception is thrown, you can catch it and process with standard try...catch statement. The threads shouldn't just terminate with no reason. Maybe you have some deadlocks in your application and your threads are just waiting? Does the number of active threads decrease? Does isAlive method return false for these threads?