#Game crashes after around 10 minutes of playtime seemingly due to memory leak

67 messages · Page 1 of 1 (latest)

quaint gull
#

after around 10 or so minutes the game crashes, it didn't before. Only thing that changed between the crashes starting was some game updates and me updating graphics driver to play another game, which works fine. The crashes happen each time i launch the game and try playing for a longer time.

quaint gull
#

also have had multiple crashes at ends of battles

quaint gull
#

heres some log photos:

#

and heres what the .dmp file says

#

this is after another crash today

quaint gull
#

was looking at ram usage, game runs normal at around 800MB, after battles it increases and at 1.2GB it crashes once battle ends, i will check that

#

so, there is a memory leak, am recording data for it, will send after it crashes the game

quaint gull
#

uhh, message got blocked

#

@pastel ingot hey, is there a way to send my data over?

#

started game - 907MB stable
searching for battle - 970MB
1 battle start - 1030 MB
1 battle end 1080 MB
after 1 battle end in ship view - 1110 MB
2 battle start - 1190MB
2 battle end - 1180MB
after 2 battle end in ship view 1190 MB
3 battle start - 1260MB
3 battle end - 1250MB
after 3 battle end in ship view - 1260MB
4 battle start - 1340MB
4 battle end - 1320MB
after 4 battle end in ship view - 1320MB
5 battle start - 1430MB
5 battle end - 1420MB
after 5 battle end in ship view - 1450MB

#

6 battle start - 1490MB
6 battle end - 1470MB
after 6 battle end in ship view - 1500MB
7 battle start - 1540MB
7 battle end - 1510MB
after 7 battle end in ship view - 1530MB
8 battle start - 1590MB
8 battle end - 1570MB
after 8 battle end in ship view - 1610MB
9 battle start - 1640MB
9 battle end - 1630MB
after 9 battle end in ship view - 1650MB
10 battle start - 1700MB
10 battle end - 1690MB
after 10 battle end in ship view - 1690MB

#

11 battle start - 1710MB
11 battle end - 1740MB
after 11 battle end in ship view - 1750MB
12 battle start - 1800MB
12 battle end - 1800MB
after 12 battle end in ship view - 1810MB
13 battle start - 1870MB
13 battle end - 1870MB
after 13 battle end in ship view - 1880MB
14 battle start - 1940MB
14 battle end - 1940MB
after 14 battle end in ship view - 1980MB
15 battle start - 2000MB
15 battle end - 1990MB

#

16 battle start - 2070MB
16 battle end - 2050MB
after 16 battle end in ship view - 2085MB
17 battle start - 2140MB
17 battle end - 2140MB
after 17 battle end in ship view - 2160MB
18 battle start - 2230MB
18 battle end - 2210MB
after 18 battle end in ship view - 2240MB
19 battle start - 2280MB
19 battle end - 2260MB
after 19 battle end in ship view - 2290MB
20 battle start - 2340MB
20 battle end - 2320MB
after 20 battle end in ship view - 2340MB

#

21 battle start - 2380MB
21 battle end - 2370MB
after 21 battle end in ship view - 2400MB
22 battle start - 2450MB
22 battle end - 2420MB
after 22 battle end in ship view - 2450MB
23 battle start - 2490MB
tabbed out mid battle and program crashed, didn't manage to record the ram at moment of crash
The program Pixel Starships.exe version 6000.0.56.31582 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

PS: after battle finishes the ram jumps up by 40MB and then slowly reduces by around 30

#

ok, managed to send it all in small chunks

#

sorry for ping

pastel ingot
#

Glad you got it, sorry was at work.

quaint gull
#

HIGHSCORE!

#

managed to capture right on crash

#

here's game version btw

clear oracle
#

@acoustic dagger 👆

quaint gull
#

Game crashes after around 10 minutes of playtime seemingly due to memory leak

quaint gull
#

can confirm that in version

#

the memory leak still exists

pastel ingot
#

Thanks for the update

quaint gull
#

error is the same before crash

#

but the way the RAM behaves is different, the way it allocates RAM during, before and after battles has changed

#

so now the game crashed at the start of the battle

quaint gull
#

another crash

quaint gull
#

lovely

#

these are ones that got a proper crash report which is around 70% of crashes

quaint gull
#

so, more people have this

slate parcel
#

I have the same FWIW... and every single error is the same

#

ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF9FE27110B)

#

interestingly, it's not "Access violation"

#

and I have no reports that have that text in

quaint gull
#

did you read the dmp file?

slate parcel
#

/tmp/SavySoda/Pixel Starships 2/Crashes
$ find -name "." | xargs grep "Access violation" | wc -l
grep: .: Is a directory
0

#

how can I read it?

#

seems binary

quaint gull
#

that will only check the player.log

slate parcel
#

like I can't read it in notepad++ 😄

quaint gull
#

to check the dmp you can through visual studio

#

or WinDbg, but i've noticed it can't properly read it

#

only visual studio was able to

slate parcel
#

VS Code can't open it : The file is not displayed in the text editor because it is either binary or uses an unsupported text encoding.

quaint gull
#

you running on a mac?

slate parcel
#

Windows

#

do I need a plugin?

quaint gull
#

hmm

#

i don't really got any for this in visual studio

slate parcel
#

I'll try IntelliJ

quaint gull
quaint gull
#

the console does also mention something about a leak

#

that message appears during battle beggining