|
|
Log in / Subscribe / Register

Developing GNOME Applications with Java (Linux Journal)

Developing GNOME Applications with Java (Linux Journal)

Posted May 29, 2005 16:50 UTC (Sun) by phiggins (guest, #5605)
In reply to: Developing GNOME Applications with Java (Linux Journal) by bluefoxicy
Parent article: Developing GNOME Applications with Java (Linux Journal)

You're really starting to sound like Colin Percival raising the red flag on hyperthreading. Maybe the fact that you can't convince VM designers to fix their problems is a sign that the problem isn't worth fixing. Take a look at BugTraq and search by narrowing to Sun as the vendor, then pick the J2SE JRE as the product. I see four vulnerabilities, and the only one that actual looks scary if the bytecode verifier, but that's not a stack overflow. I used to be worried about buffer overflows in the VM being exploitable from Java code, but I was concerned about that well over 5 years ago and such an exploit has never appeared. So what are you surprised that the VM writers aren't jumping through all the hoops you are proposing to prevent it from ever happening?

The much bigger problem with JIT is the huge amount of non-shared memory that gets taken up by JIT compiled versions of the (huge!) standard libraries. I'd much rather see someone go for a shared mmap()able temp file for the purpose of reducing memory usage!


to post comments

Developing GNOME Applications with Java (Linux Journal)

Posted May 29, 2005 17:15 UTC (Sun) by cajal (guest, #4167) [Link] (1 responses)

In fact, Sun's Java 5.0 VM has started to share libraries between different instances of the JRE. See this article for more information.

Developing GNOME Applications with Java (Linux Journal)

Posted May 31, 2005 20:24 UTC (Tue) by massimiliano (subscriber, #3048) [Link]

In fact, Sun's Java 5.0 VM has started to share libraries between different instances of the JRE.

Mono does this if you compile AOT (and so does .NET if you use ngen).

Developing GNOME Applications with Java (Linux Journal)

Posted May 31, 2005 23:56 UTC (Tue) by mjw (subscriber, #16740) [Link]

The much bigger problem with JIT is the huge amount of non-shared memory that gets taken up by JIT compiled versions of the (huge!) standard libraries. I'd much rather see someone go for a shared mmap()able temp file for the purpose of reducing memory usage!
Use GCJ. The libgcj (GNU Classpath) core libraries are just compiled as a shared library so all gcj compiled (native) applications just share the core class library. That is what is so nice about the radical traditional approach that gcj takes.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds