← Back to context Comment by nevdka 15 hours ago Then there’s perl, which doesn’t free at all. 17 comments nevdka Reply hedora 14 hours ago Perl frees memory. It uses refcounting, so you need to break heap cycles or it will leak.(99% of the time, I find this less problematic than Java’s approach, fwiw). cermicelli 15 hours ago Freedom is overrated... :P NooneAtAll3 15 hours ago doesn't java also?I heard that was a common complaint for minecraft adgjlsfhk1 8 hours ago Minecraft for somewhat silly reasons was largely stuck using Java8 for ~a decade longer than it should have which meant that it was using some fairly outdated GC algorithms. NooneAtAll3 1 hour ago "silly reasons" being Java breaking backwards compatibilitydecade seems a usual timescale for that, considering f.e. python 2->3 xxs 15 hours ago What do you mean - if Java returns memory to the OS? Which one - Java heap of the malloc/free by the JVM? cogman10 14 hours ago Java is pretty greedy with the memory it claims. Especially historically it was pretty hard to get the JVM to release memory back to the OS.To an outsider, that looks like the JVM heap just steadily growing, which is easy to mistake for a memory leak. 10 replies →
hedora 14 hours ago Perl frees memory. It uses refcounting, so you need to break heap cycles or it will leak.(99% of the time, I find this less problematic than Java’s approach, fwiw).
NooneAtAll3 15 hours ago doesn't java also?I heard that was a common complaint for minecraft adgjlsfhk1 8 hours ago Minecraft for somewhat silly reasons was largely stuck using Java8 for ~a decade longer than it should have which meant that it was using some fairly outdated GC algorithms. NooneAtAll3 1 hour ago "silly reasons" being Java breaking backwards compatibilitydecade seems a usual timescale for that, considering f.e. python 2->3 xxs 15 hours ago What do you mean - if Java returns memory to the OS? Which one - Java heap of the malloc/free by the JVM? cogman10 14 hours ago Java is pretty greedy with the memory it claims. Especially historically it was pretty hard to get the JVM to release memory back to the OS.To an outsider, that looks like the JVM heap just steadily growing, which is easy to mistake for a memory leak. 10 replies →
adgjlsfhk1 8 hours ago Minecraft for somewhat silly reasons was largely stuck using Java8 for ~a decade longer than it should have which meant that it was using some fairly outdated GC algorithms. NooneAtAll3 1 hour ago "silly reasons" being Java breaking backwards compatibilitydecade seems a usual timescale for that, considering f.e. python 2->3
NooneAtAll3 1 hour ago "silly reasons" being Java breaking backwards compatibilitydecade seems a usual timescale for that, considering f.e. python 2->3
xxs 15 hours ago What do you mean - if Java returns memory to the OS? Which one - Java heap of the malloc/free by the JVM? cogman10 14 hours ago Java is pretty greedy with the memory it claims. Especially historically it was pretty hard to get the JVM to release memory back to the OS.To an outsider, that looks like the JVM heap just steadily growing, which is easy to mistake for a memory leak. 10 replies →
cogman10 14 hours ago Java is pretty greedy with the memory it claims. Especially historically it was pretty hard to get the JVM to release memory back to the OS.To an outsider, that looks like the JVM heap just steadily growing, which is easy to mistake for a memory leak. 10 replies →
Perl frees memory. It uses refcounting, so you need to break heap cycles or it will leak.
(99% of the time, I find this less problematic than Java’s approach, fwiw).
Freedom is overrated... :P
doesn't java also?
I heard that was a common complaint for minecraft
Minecraft for somewhat silly reasons was largely stuck using Java8 for ~a decade longer than it should have which meant that it was using some fairly outdated GC algorithms.
"silly reasons" being Java breaking backwards compatibility
decade seems a usual timescale for that, considering f.e. python 2->3
What do you mean - if Java returns memory to the OS? Which one - Java heap of the malloc/free by the JVM?
Java is pretty greedy with the memory it claims. Especially historically it was pretty hard to get the JVM to release memory back to the OS.
To an outsider, that looks like the JVM heap just steadily growing, which is easy to mistake for a memory leak.
10 replies →