edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] jspool
Date: Sun, 13 Aug 2017 14:29:20 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1708131422210.17661@carhart.net> (raw)
In-Reply-To: <20170713073152.eklhad@comcast.net>



> duktape doesn't have a pool of a fixed size, it allocates what it needs. Duh!

This is great!  Occasionally I will hit the message about cannot allocate 
more memory.  And I also think that ability to allocate memory dynamically 
could be another test that site-makers put the client through in order to 
call the bluff of user-agent spoofers, in addition to things like styles 
and testing the decimal places on numbers.


  reply	other threads:[~2017-08-13 21:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 11:31 Karl Dahlke
2017-08-13 21:29 ` Kevin Carhart [this message]
     [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=alpine.LRH.2.03.1708131422210.17661@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).