On Thu, 11 Apr 2024 at 09:39, Jens Zurawski wrote:
> A class static member is never freed, once the
> class is loaded.
A pedantic nitpick! :-)
A class static member can be freed, when the classloader is eligible
for GC. In the context of NetBeans modules, OSGi, etc. then that
could be
Others already have written good points to this question. I just want to
add my 2 cents.
Netbeans is doing a lot of stuff in the background and it's using a
significant amount of RAM for speeding things up. A professor of mine
once said something like "If you have a lot of RAM and you don't
I've been writing Java applications since around 1995 and I have written many
sizable ones that didn't require a huge amount of RAM. Of course the JVM
itself is a fixed overhead which is now, what, 50MB? (but even that can be
ameliorated via modularization these days), and more and more
That's the question I've asked myself for years... In the first versions of
Java that was a concern: Why did Netbeans use 200MB of RAM when Visual
Basic used just 10MB or less? PC's were more limited in RAM, maybe that's
why Java was not popular in desktop apps, but succeeded with web
servers,
Can you give an example of this using "extreme amounts of RAM for simple
apps"? We're talking something more involved than HelloWorld, but not
quite toy-examples/src/viewers/MandelbrotJuliaViewer.java at main ·
Alonso-del-Arte/toy-examples · GitHub
Why does Java and Netbeans use extreme amounts of RAM for simple apps?
Can there be done something about it?
-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail:
