Re: [Edbrowse-dev] createJavacontext

[Adam Thompson <arthompson1990@gmail.com>]

On Tue, Feb 11, 2014 at 12:12:23PM -0500, Karl Dahlke wrote:
> If the js runtime or context or global window cannot be created,
> it prints a message to that effect, leaves jss null, and returns.
> This is the first non-exit error leg in our js world.
> Without the context, javascript is disabled,
> but edbrowse continues to run.
> You can test this easily.
> Edit Chris memory hogging array program and another html file.
> Browse the first and get the memory full error.
> Switch to buffer 2 and browse the second,
> but there isn't enough memory to set up the window,
> so the context is not created, jss is null,
> and any javascript features in that second file,
> like onclick push buttons, won't work.

Yep, works well. I tried this with the array html program and jsrt.
Edbrowse didn't exit and javascript stopped as expected.

> This is I think the start of where we want to go.
> Other error legs will print a message,
> distroy context, set jss to null, and return.

Yep, sounds good. In the future it'd be nice if there was some way of
recovering a working js set up in some of these cases (e.g.
when js has run out of memory), but I can't think of a robust way at the moment,
and this is certainly a vast improvement.

Cheers,
Adam.