Attila Szegedi a écrit : > Your idea wouldn't be bad as such, except for few devils in details: > - The code of the java.lang.ClassLoader class (at least in Sun's > implementation) is engineered so that you just can't override the > behaviour where it strongly references each Class object it creates. > - And then there's also the problem that if you try to get around this > (say, using a custom ClassLoader code using a different boot class > path, or resorting to reflection (with access checks off) to get to > that Vector object and remove Class objects manually from it), the JVM > typically becomes very unstable very quickly (crashes in native > code)... Been there :-) > > Attila. > > Attila, the VM doesn't become unstable, it crashes reproducibly in the GC collection. Perhaps because the object layout in lost.
Rémi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
