On Fri, Feb 07, 2014 at 10:23:05AM -0800, Chris Brannon wrote: > Karl Dahlke <[email protected]> writes: > > My gut tells me the segfaults might come from somewhere else. > So it is failing with out-of-memory in this case. I'm sure youtube is a > very JS-intensive site, but could there be another reason for the memory > exaustion? I don't know.
Not sure, we really need to go through everything and ensure that what needs to be rooted is and what doesn't isn't. Incidentally I bumped my jspool limit up to 64 meg and that example works now. Really it'd be much nicer if we could get js to dynamically grow to deal with this (with an *optional* limit). I'd still prefer it if it just killed the offending context as well (js_DestroyContext and js_GC?). This should mean that everything else can continue and we reclaim the lost memory, or in the worst case just the js side is broken. Either way, it allows the user to save critical work, bookmark pages etc. At the moment, although I agree that not segfaulting is much nicer, the overall outcome is the same; edbrowse goes away taking your unsaved work and other browsing sessions with it. I can try and implement this if people agree. Cheers, Adam. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
