From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] jspool
Date: Sun, 13 Aug 2017 07:31:52 -0400 [thread overview]
Message-ID: <20170713073152.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
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
next reply other threads:[~2017-08-13 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 11:31 Karl Dahlke [this message]
2017-08-13 21:29 ` Kevin Carhart
[not found] ` <20170713174445.eklhad@comcast.net>
2017-08-13 23:01 ` Kevin Carhart
[not found] ` <20170713191620.eklhad@comcast.net>
2017-08-13 23:38 ` [Edbrowse-dev] test #0 Kevin Carhart
2017-08-14 0:54 ` Karl Dahlke
2017-08-14 0:59 ` Kevin Carhart
[not found] ` <20170713220453.eklhad@comcast.net>
2017-08-14 4:54 ` [Edbrowse-dev] explanation of patch 20170813 Kevin Carhart
-- strict thread matches above, loose matches on Subject: below --
2014-02-07 20:12 [Edbrowse-dev] jspool Karl Dahlke
2014-02-07 21:38 ` Chris Brannon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170713073152.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).