summaryrefslogtreecommitdiff
path: root/test/372
diff options
context:
space:
mode:
Diffstat (limited to 'test/372')
-rw-r--r--test/37272
1 files changed, 72 insertions, 0 deletions
diff --git a/test/372 b/test/372
new file mode 100644
index 0000000..b0acf3a
--- /dev/null
+++ b/test/372
@@ -0,0 +1,72 @@
+Return-Path: <messages-bounces@vassalengine.org>
+X-Original-To: uckelman@nomic.net
+Delivered-To: uckelman@nomic.net
+Received: from one.vassalengine.org (one.vassalengine.org [66.253.49.171])
+ by charybdis.ellipsis.cx (Postfix) with ESMTP id 265171008C
+ for <uckelman@nomic.net>; Wed, 10 Nov 2010 10:42:30 -0700 (MST)
+Received: from one.vassalengine.org (localhost [IPv6:::1])
+ by one.vassalengine.org (Postfix) with ESMTP id A6F3ECE;
+ Wed, 10 Nov 2010 10:42:29 -0700 (MST)
+X-Original-To: messages@vassalengine.org
+Delivered-To: messages@vassalengine.org
+Received: from charybdis.ellipsis.cx (charybdis.ellipsis.cx [66.253.49.165])
+ by one.vassalengine.org (Postfix) with ESMTP id 339CC9B
+ for <messages@vassalengine.org>; Wed, 10 Nov 2010 10:42:26 -0700 (MST)
+Received: by charybdis.ellipsis.cx (Postfix, from userid 500)
+ id 587BD100B5; Wed, 10 Nov 2010 10:42:25 -0700 (MST)
+To: messages@vassalengine.org
+In-reply-to: <1289408163.20521.1933.bridge@www.vassalengine.org>
+References: <1286189102.20134.1513.bridge@www.vassalengine.org>
+ <1289408163.20521.1933.bridge@www.vassalengine.org>
+Comments: In-reply-to pgeerkens <pgeerkens@hotmail.com>
+ message dated "Wed, 10 Nov 2010 09:56:03 -0700."
+From: Joel Uckelman <uckelman@nomic.net>
+Date: Wed, 10 Nov 2010 18:42:24 +0100
+Message-Id: <20101110174225.587BD100B5@charybdis.ellipsis.cx>
+Subject: Re: [messages] [Developers] Re: determining how much heap a
+ BufferedImage uses
+X-BeenThere: messages@vassalengine.org
+X-Mailman-Version: 2.1.12
+Precedence: list
+Reply-To: messages@vassalengine.org
+List-Id: <messages.vassalengine.org>
+List-Unsubscribe: <http://www.vassalengine.org/mailman/options/messages>,
+ <mailto:messages-request@vassalengine.org?subject=unsubscribe>
+List-Archive: <http://www.vassalengine.org/pipermail/messages/>
+List-Post: <mailto:messages@vassalengine.org>
+List-Help: <mailto:messages-request@vassalengine.org?subject=help>
+List-Subscribe: <http://www.vassalengine.org/mailman/listinfo/messages>,
+ <mailto:messages-request@vassalengine.org?subject=subscribe>
+MIME-Version: 1.0
+Content-Type: text/plain; charset="us-ascii"
+Content-Transfer-Encoding: 7bit
+Sender: messages-bounces@vassalengine.org
+Errors-To: messages-bounces@vassalengine.org
+X-Bogosity: Unsure, tests=bogofilter, spamicity=0.500000, version=1.2.0
+
+Thus spake pgeerkens:
+> I believe it is the heap manager causing the problem, not the buffered
+> image itself. I get the following output
+> 640
+> 240
+> 16
+> from the code below with min/max heap set to 961MB, totalling 896MB of
+> the 961MB available. When I bump the size factor in img3 to 0.2 I run
+> out of heap.
+
+I'm having trouble interpreting your results here. Your program is
+not the same as mine---the first image can't be garbage collected
+yet when you load the second image, and that will affect how much
+heap is still available.
+
+What are the minimum heap sizes you can run at when you use the
+same program and parameters as I used?
+
+
+--
+J.
+_______________________________________________
+messages mailing list
+messages@vassalengine.org
+http://www.vassalengine.org/mailman/listinfo/messages
+