diff options
| author | uckelman <uckelman@nomic.net> | 2010-11-10 22:49:08 +0000 |
|---|---|---|
| committer | uckelman <uckelman@nomic.net> | 2010-11-10 22:49:08 +0000 |
| commit | c1b8e6bda64c4a8f3b9875cf7e3387510b7aadad (patch) | |
| tree | 94013143614184ac32528c25832d7adeb9e693c0 /test/372_flat | |
| parent | 6390daa3862f68ca9e9231d38d1145f4133f7ebd (diff) | |
Added additional message.
git-svn-id: https://vassalengine.svn.sourceforge.net/svnroot/vassalengine/site-src/trunk@7458 67b53d14-2c14-4ace-a08f-0dab2b34000c
Diffstat (limited to 'test/372_flat')
| -rw-r--r-- | test/372_flat | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/test/372_flat b/test/372_flat new file mode 100644 index 0000000..eb0c7bf --- /dev/null +++ b/test/372_flat @@ -0,0 +1,27 @@ +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 + + |