Opened 4 years ago
Last modified 3 years ago
#11758 closed defect
PEGASUS: colossal memory leak, wan't start — at Version 11
Reported by: | fedor4ever | Owned by: | sev- |
---|---|---|---|
Priority: | high | Component: | Engine: Pegasus |
Version: | Keywords: | ||
Cc: | Game: | Journeyman Project Pegasus Prime |
Description (last modified by )
scummvm-2.2.0-winxp-win32>scummvm.exe -v
ScummVM 2.2.0 (Sep 14 2020 10:41:13)
mingw-w64-master-9a33d895>scummvm.exe -v
ScummVM 2.3.0git12153-g9a33d895ed (Feb 5 2021 05:21:58)
Features compiled in: TAINTED Vorbis FLAC MP3 RGB zLib MPEG2 FluidSynth Theora AAC A/52 FreeType2 JPEG PNG cloud (servers, local) TinyGL OpenGL (withshaders) GLEW
mingw-w32-master-9a33d895>scummvm.exe -v
ScummVM 2.3.0git12153-g9a33d895ed (Feb 5 2021 06:22:42)
Features compiled in: TAINTED Vorbis FLAC MP3 RGB zLib MPEG2 FluidSynth Theora AAC A/52 FreeType2 JPEG PNG cloud (local) TinyGL OpenGL (with shaders) GLEW
Tried Symbian build
How reproduce: run demo, push Start button to run game,instead intro memory start leaking. This leak consume almost 2Gb Ram!
Os: windows, symbian.
ScummVM 1.8.1 run demo fine.
Change History (11)
comment:1 by , 4 years ago
Owner: | set to |
---|---|
Resolution: | → worksforme |
Status: | new → pending |
comment:2 by , 4 years ago
Priority: | high → low |
---|
comment:3 by , 4 years ago
First line in description: scummvm-2.2.0-winxp-win32
It means ScummVM 2.2.0 32 bit edition.
I try run Pegasus demo with ScummVM 2.2.0 on my symbian phone with memory monitor and see 2 things: black screen and free ram started disappear. App crashed when 10mb free ram ends.
I try 1.8.1 - memory doesn't disappear, demo runs fine.
I run Pegasus with on winxp x64 sp2 with task manager started. I see black screen free ram started disappear. When it feed 1974mb ram it stopped. No sounds, only black screen.
Do you say on mac os game use 400 mb? Can you try 1.8.1? I haven't mac.
comment:4 by , 4 years ago
I tried the demo on Linux with both the current master and branch-2-2, and I can't see any issue. With branch-2-2, it uses 14.1 Mb before starting the game, and then a steady 22.7 Mb while playing. With master it uses a little more memory, 14.6 Mb before starting the game, and then 23.0 Mb while playing. And in both cases I still have plenty of free memory.
I also tried with valgrind, and it didn't detect any memory leak in the pegasus engine.
comment:5 by , 4 years ago
And I also just tried on macOS 64 bits on branch-2-2 and while playing the pegasus prime demo ScummVM uses a steady 61.6 Mb (it uses 46.7 Mb before starting the game).
So I can't reproduce any bad memory leak either (neither on Linux, nor on mac).
comment:6 by , 4 years ago
Do you press start button? Do you try windows build? Try x64 version on win7 x64 - memory leaked too.
comment:7 by , 4 years ago
Yes I did press the Start button.
And no I did not try the windows build (and I can't try it since I don't have a Windows computer).
comment:9 by , 3 years ago
Summary: | Pegasus prime demo: colossal memory leak, wan't start → PEGASUS: colossal memory leak, wan't start |
---|
comment:10 by , 3 years ago
Resolution: | worksforme → fixed |
---|---|
Status: | pending → closed |
comment:11 by , 3 years ago
Description: | modified (diff) |
---|---|
Priority: | low → high |
Resolution: | fixed |
Status: | closed → new |
Still crashes.
Tried:
mingw-w64-master-9a33d895>scummvm.exe -v
ScummVM 2.3.0git12153-g9a33d895ed (Feb 5 2021 05:21:58)
Features compiled in: TAINTED Vorbis FLAC MP3 RGB zLib MPEG2 FluidSynth Theora AAC A/52 FreeType2 JPEG PNG cloud (servers, local) TinyGL OpenGL (withshaders) GLEW
mingw-w32-master-9a33d895>scummvm.exe -v
ScummVM 2.3.0git12153-g9a33d895ed (Feb 5 2021 06:22:42)
Features compiled in: TAINTED Vorbis FLAC MP3 RGB zLib MPEG2 FluidSynth Theora AAC A/52 FreeType2 JPEG PNG cloud (local) TinyGL OpenGL (with shaders) GLEW
Symbian build 74fd09e830211de9c138b43e475f74b014942586 crashes too.
I cannot reproduce. The memory usage goes from initial 300MB, eventually to 700MB. Did not see 2Gb on a 64bit Mac.
Please, provide more information. Also, since you're a developer, please run a MemoryDoctor on Windows and tell where do you see the memory leaks.