bugGlobulation 2 - Bugs: bug #19601, gigantic memory usage increase to...

 
 

bug #19601: gigantic memory usage increase to load maps in 0.8.22

Submitter:  Joe Wells <jbw>
Submitted:  Mon 16 Apr 2007 06:28:35 AM UTC
   
 
Severity:  3 - Normal Status:  Fixed
Assigned to:  None Open/Closed:  Closed
Release:  None Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 27 Apr 2007 07:04:41 PM UTC, comment #2: 

I'm glad to hear the problem can be reproduced.

I don't think it is an issue of "trimming the fat".  The amount of memory used went up by a factor of at least 20 from version 0.8.21 to 0.8.22.  That sounds like a bug to me.

Joe Wells <jbw>
Fri 20 Apr 2007 08:14:31 PM UTC, comment #1: 

I see something similar occurring in 0.8.23.

I created a 512x512 map in the editor, uniform terrain (sand).

Looked at memory while editing the one I just created, found it was using about 80MB.  Then I left the editor and reopened the map in the editor.  glob2 was then using around 450MB of RAM.

Perhaps 0.8.23 is slightly better, but more can probably be done to trim the fat.

Anonymous
Mon 16 Apr 2007 06:28:35 AM UTC, original submission:  

glob2 version 0.8.22 uses more than a gigabyte of memory just to edit
or play an already-existing 512 by 512 map it created.  The virtual
memory used is about 1.6 gigabytes.  Shortly after loading the map it
reports around 1.0 to 1.2 gigabytes resident, which I assume means
that other programs running on the machine needed to quickly reclaim
half a gigabyte just to keep running.  Basically everything else on my
machine gets paged or swapped out during the process of loading the
map, which takes quite some time.  After I quit the game or editor, it
appears that all of the memory is recovered because glob2 goes back
down to 50 megabytes of virtual memory (the amount it was using before
entering the editor).

Note that I can use glob2 version 0.8.22 to create a 512 by 512 map
using only 80 megabytes of virtual memory.  However, after I save the
map in a file and exit the initial editor session, if I try to load
the new map again to edit or play it, the memory usage goes to 1.6
gigabytes again.

In comparison, glob2 version 0.8.21 uses about 80 megabytes virtual
memory and about 60 megabytes resident memory to edit a 512 by 512
map.  And glob2 version 0.8.21 plays a 512 by 512 map using about 170
megabytes virtual memory and about 120 megabytes resident memory.  I
have never seen glob2 version 0.8.21 use more than 180 megabytes of
virtual memory.

This is a memory usage increase of about a factor of 20.  The
difference shows in that it takes just a couple of seconds to load a
512 by 512 map with 0.8.21, but up to a minute for 0.8.22.

I thank Kai and Steph for giving me feedback on my e-mail discussing
this problem.

Joe Wells <jbw>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by genixpro (Updated the item)
  • -email is unavailable- added by jbw (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-07-27 genixpro StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code