harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pervov" <pmcfi...@gmail.com>
Subject Re: [jira] Closed: (HARMONY-927) DRLVM's DestroyVM needs to be more robust
Date Fri, 21 Jul 2006 10:58:25 GMT
On 7/20/06, Oliver Deakin <oliver.deakin@googlemail.com> wrote:
> I agree Pavel - it should be fixed in the launcher. But, as I said in
> [1], we should
> give some consideration to the fact that the RI and IBM vms exit
> gracefully
> under the same circumstances, and that perhaps we should also try to
> fix this in the drlvm to match their behaviour.

Not sure how do you know about RI... :)
This is a sort of compatibility with user code though rather than following
some spec.

I started to think of ways simply calling ExceptionClear wouldnt result
> in a clean exit from drlvm. An OutOfMemoryError followed by DestroyJavaVM
> would probably still result in a failure in VMStart, so just calling
> ExceptionClear might not be enough to guarantee clean exit

It is then the problem of VMStart to be able to work in strict memory (or
even out-of-memory) conditions. :) Let's not mix things.

> Thinking about this makes me wonder how drlvm will exit cleanly when
> there is an
> OutOfMemoryError when running it from the drlvm launcher. If the heap
> is full, surely trying to run shutdown code in VMStart is dangerous
> anyway?

VMStart.shutdown() will most probably throw OutOfMemoryError itself. But I'm
not sure how it may be dangerous.

    Pavel Pervov.
Intel Middleware Products Division.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message