From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] segfault with small pool
Date: Wed, 19 Feb 2014 11:28:28 +0000 [thread overview]
Message-ID: <20140219112828.GI28870@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140119042137.eklhad@comcast.net>
On Wed, Feb 19, 2014 at 04:21:37AM -0500, Karl Dahlke wrote:
> I sometimes run with jspool = 2 just to test,
> just to see what happens with a real world memory error.
Good idea.
[snip]
> Set jspool = 2 and type or read in these two commands.
>
> b http://en.wikipedia.org/wiki/http
> b http://en.wikipedia.org/wiki/https
>
> I get something like this.
>
> edbrowse ready
> .
> 180413
> .
> 34837
Wow, mine explodes on this one.
> .
> 135113
> .
> could not allocate memory for javascript operations.
> out of memory
Why haven't we stopped here?
Anything from this point on is probably going to go wrong.
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> could not allocate memory for javascript operations.
> out of memory
> Unrecoverable JavaScript error in this session
And it does.
> *** glibc detected *** /home/eklhad/bin/edbrowse: free(): corrupted unsorted chunks: 0x0a4ca310 ***
> ======= Backtrace: =========
Ugh, double free? Not sure, have switched javaSessionFail to use
freeJavaContext in case.
Thanks for the testing, I'm currently going thrpough jsloc.cpp trying to fix things.
Cheers,
Adam.
next prev parent reply other threads:[~2014-02-19 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 9:21 Karl Dahlke
2014-02-19 11:28 ` Adam Thompson [this message]
2014-02-19 11:38 ` Adam Thompson
2014-02-19 14:12 ` Adam Thompson
2014-02-19 16:07 ` Chris Brannon
2014-02-19 16:52 ` Adam Thompson
2014-02-19 17:34 ` Chris Brannon
2014-02-19 21:04 ` Adam Thompson
2014-02-19 16:36 Karl Dahlke
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=20140219112828.GI28870@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--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).