URL:
<http://gna.org/bugs/?11022>
Summary: option --lowmem leading to increased memory usage
(maybe a gcc 4.2.x bug?)
Project: Battle for Wesnoth
Submitted by: ivanovic
Submitted on: Samstag 09.02.2008 um 18:54
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None of the others
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.3.15+svn, r23638
Operating System: linux
_______________________________________________________
Details:
When using the configure option --lowmem the memory actually does increase
instead of being reduced. The changes when setting lowmem are basically using
different compiler flags* and deactivated teamcolor resulting in all units
being pink instead of being colored. Maybe it does also set some other stuff,
I don't know.
I suspect the compiler flag being faulty so that other gcc versions are not
affected. Though it would be nice to get some data for this. At least chrber
was able to reproduce this problem using current trunk and gcc 4.2.3, still
it is the same 4.2.x line.
So if this is a general problem, we should probably drop this configure
option, not sure though.
My system specs that might be needed:
$CXXFLAGS=-march=nocona -O2 -pipe -fomit-frame-pointer
gcc-Version 4.2.2 (Gentoo 4.2.2 p1.0)
configure line (for the later test, add --enable-lowmem):
./autogen.sh --bindir=/games-bin --datadir=/games/ --enable-editor
--enable-server --with-preferences-dir=.wesnoth-svn --program-suffix=-svn
--with-datadir-name=wesnoth-svn --enable-dummy-locales
Some ways to reproduce (and some numbers):
Way 1 to reproduce:
1) Start Wesnoth, feel free to add acceleration at 8x.
2) Start Two Brothers on easy, have a look at all the map (to have all map
data in ram, too) and :droid yourself. Once the game is over, have a look at
ram usage (eg using top). For me ram usage it at about 95 to 100MB at this
point of time.
3) Recompile Wesnoth using ./configure --lowmem.
4) Do the same steps as before. It results in a ram usage of about 107MB.
Which is higher than the old 95 to 100MB.
Way 2 to reproduce:
1) Start your "normal" Wesnoth and load the attached replay (my_replay.gz).
Directly click on play, once it is over watch the ram usage. For me it is
around 100MB.
2) Recompile wesnoth using --enable-lowmem.
3) Start the new Wesnoth and load the attached replay. After watching it all
through, ram usage might be higher than without that flag. For me ram usage
goes to 124MB.
* This is the respective block from configure.ac:
if test "x$lowmem" = "xyes"
then
CPPFLAGS="$CPPFLAGS -DLOW_MEM"
fi )
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Samstag 09.02.2008 um 18:54 Name: my_replay.gz Size: 54kB By:
ivanovic
Replay to reproduce using way 2
<http://gna.org/bugs/download.php?file_id=3776>
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?11022>
_______________________________________________
Nachricht geschickt von/durch Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
