You know what's funny? I finally got rid of the old jspool parameter. Remember we had to set the size of the js pool at startup? We had to anticipate, guess, how much space edbrowse would need for js, and if we were in edbrowse all day and browsed yet one more site with lots of js, boom! Well we don't have to worry about that any more. duktape doesn't have a pool of a fixed size, it allocates what it needs. Duh! So jspool is a nice thing to leave behind.
I left the memory hog test in jsrt for now. Push the memorry fill button and it creates 20 million objects no problem. Although, ha ha, it prints a counter every 10,000 objects, which is fine for me, but my wife finally told me that alert on any other browser is not the same as print, it's a message that you have to acknowledge before you can move on. Sometimes I'm at a real disadvantage never running a regular browser. Nobody would want to click ok 200 times, so maybe I should remove that status alert. Well nobody runs jsrt on a regular browser, except Geoff, cause he's curious. Karl Dahlke
_______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
