Page 2 of 2
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Tue Jan 11, 2022 5:19 pm
by o01eg
wobbly wrote: ↑Mon Jan 10, 2022 3:12 pm
Ophiuchus wrote: ↑Sun Jan 09, 2022 10:02 pm
based on the behaviour (no interaction with the game) i guess the follwing commit could be the culprit?
is this already bad?:
commit fb38731469610571e01bbda674bad396be797bc5
-de-pointerize RenderCache
-don't redundantly create RenderState objects when one was passed into Font::PreRenderText
and this one still good?
commit ff62820ae17d425b7e9fabd25981333f500b3db5
reserve slightly more space in vertex buffer, which was often one smaller than required
Yes this is correct.
Could you run the game in debugger?
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Tue Jan 11, 2022 5:22 pm
by wobbly
o01eg wrote: ↑Tue Jan 11, 2022 5:19 pm
Could you run the game in debugger?
Maybe. Not sure how to do that.
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Tue Jan 11, 2022 5:43 pm
by Oberlus
wobbly wrote: ↑Tue Jan 11, 2022 5:22 pm
o01eg wrote: ↑Tue Jan 11, 2022 5:19 pm
Could you run the game in debugger?
Maybe. Not sure how to do that.
In Linux, preferably with a binary compiled with -g for better info:
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Wed Jan 12, 2022 12:34 am
by Oberlus
Another crash here.
I installed 8f700e9 in Windows (first update since last MP game), played a few turns and went AFK for 10 minutes, and FO was still running. Then I minimized the FO window, played Starcraft for 30 minutes, exited SC, maximized FO and it showed me a white screen, with the UI sounds of the mouse passing over buttons and whatnot. Then I minimized and maximized again, screen was black this time and FO crashed (I got 7 different windows about FO crashing, which might be related to the number of players, 6 AIs + I).
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Wed Jan 12, 2022 3:43 am
by wobbly
Oberlus wrote: ↑Tue Jan 11, 2022 5:43 pm
wobbly wrote: ↑Tue Jan 11, 2022 5:22 pm
o01eg wrote: ↑Tue Jan 11, 2022 5:19 pm
Could you run the game in debugger?
Maybe. Not sure how to do that.
In Linux, preferably with a binary compiled with -g for better info:
I'm on Windows not linux, though I believe I can still use gdb in MinGW. Not sure how to compile with -g, I'm using visual studios and just clicking on build solution.
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Wed Jan 12, 2022 8:04 am
by Oberlus
I have no idea about how to do anything in Windows apart from installing games. Someone else please helps wobbly?
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Wed Jan 12, 2022 5:04 pm
by o01eg
wobbly wrote: ↑Wed Jan 12, 2022 3:43 am
I'm on Windows not linux, though I believe I can still use gdb in MinGW. Not sure how to compile with -g, I'm using visual studios and just clicking on build solution.
I suppose in Visual Studio should be Debug configuration and Run in debugger or something.
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Sun Jan 16, 2022 9:04 am
by Geoff the Medio
I've reverted fb38731 in
b553bcc. Can you check if the latest master still crashes?
o01eg wrote: ↑Wed Jan 12, 2022 5:04 pmwobbly wrote: ↑Wed Jan 12, 2022 3:43 am
I'm on Windows not linux, though I believe I can still use gdb in MinGW. Not sure how to compile with -g, I'm using visual studios and just clicking on build solution.
I suppose in Visual Studio should be Debug configuration and Run in debugger or something.
The MSVS solutions have debug symbols enabled for most projects (ie. not parsers) in release mode, so can be run with the debugger attached and often usefully catch exceptions and crashes.
Re: Crash ( test build (build 2022-01-04.0a71f9c) )
Posted: Sun Jan 16, 2022 2:34 pm
by wobbly
Geoff the Medio wrote: ↑Sun Jan 16, 2022 9:04 am
I've reverted fb38731 in
b553bcc. Can you check if the latest master still crashes?
Its the same as
0f4272d right? That's working.
5227769 is also working.
I'm going to play for awhile tonight just to double check no problems crop up, but otherwise seems all good.