On Wed, Feb 19, 2014 at 09:09:36PM +0000, Adam Thompson wrote: > On Wed, Feb 19, 2014 at 03:39:12PM -0500, Karl Dahlke wrote: > > Maybe ... in javaSessionFail just print and set a flag, > > Then return because of the error condition. > > The calling function might then return because of the error, > > and so on, unwinding the stack all the way back to html. > > So there was an error but cw->jss is still there.
Implemented the setting of the flag (cw->js_fail) and now have a freeJavaContext call in browseCurrentBuffer if js has died. This fixes the segfault you reported earlier (at least in my test). However, I've now run into another out of memory condition which isn't triggering javaSessionFail etc which I need to look into. I've pushed my latest progress, though I know I need to re-indent things once all this is sorted. Cheers, Adam. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
