From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by hurricane.the-brannons.com (Postfix) with ESMTP id 7645978534 for ; Sun, 23 Feb 2014 14:58:08 -0800 (PST) Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta04.westchester.pa.mail.comcast.net with comcast id VyGn1n0011swQuc54yxAng; Sun, 23 Feb 2014 22:57:10 +0000 Received: from eklhad ([107.5.36.150]) by omta15.westchester.pa.mail.comcast.net with comcast id VyxA1n00L3EMmQj3byxAU6; Sun, 23 Feb 2014 22:57:10 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Sun, 23 Feb 2014 17:57:11 -0500 Message-ID: <20140123175711.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393196230; bh=8TU2a8IR6Hlu65ZvDy59h2E1pMihPyENi74EPdsAQzo=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=qQKlBXQCInULVDt70WWWaCeAEeUanNVXVaphki1YMEqvuEMPzYTGi3TrcuMudm9t2 fpwd1oCspaVnRwxDvxhB2mCppaCQ9Hoth8i48dJqZk8N4IxkwIu62o5XS/hdpC/J// S6XJhwHsJfMhwplZieHd3WKNS7jjyi0Zgjg6WCA14iSTeiKAMM3MB2PAWgodW/fF/u 1RDVb5wML9+2VgpEVFBTzRKVZp51wP8qWxDyLTopjKpB21IhAozoUL7aq71TkGhTTg sNdAqFhajWUNOpzipXDVrur3vKWcGjaKR0I/WU3UYTpHtTZ0RD1Op1GdHAa3F+t3/E p+lyS3zovKXQQ== Subject: [Edbrowse-dev] memory error X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Dahlke List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 22:58:08 -0000 > Out of interest are there really cases where the error number > doesn't reflect the out of memory condition but the message does? I think the memory hog test in jsrt is one such. Karl Dahlke