>>105942994>cniles think they're better at managing memory that the VMThey are, without any restrictive qualifiers.
You're better off just never freeing anything with C than to use Java.
(Just let the OS swap out any unused code pages, and then restart the app every week or so).
Java's modus operandi is to just "leak memory" and then try and clean it up at some point in the future.
You can still get un gc() able memory, and they are an absolute bear to fix because "it's not supposed to happen" but it does.
First 6 months of deploying a big Java-based commercial application (that your company paid $500,000 for) is picking a garbage collector and tweaking it and monitoring it 24/7 on a godddamn pager in case it craters or starts thrashing (which usually takes a day or so).