I am getting frequent program crashes with the new build dated 2017-01-06. It seems to crash randomly around every 5 - 30 turns. Crashes are not yet reproducible; I can load an autosave from the turn before the crash and it plays successfully. I reinstalled the previous version of Freeorion (2016-12-26) and loaded an autosave from the 2017-01-06 version the and was able to play it for a hundred turns without crashing. Reinstalled the new version, loaded an autosave, and it crashed within 10 turns.
The windows application error log shows:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: FreeOrion.exe
P2: 0.0.0.0
P3: 586f8bae
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: a84d8dff
P8: c0000005
P9: 00000008
P10:
This is on a Win7 machine.
2017-01-06 build crashing frequently
Moderator: Oberlus
Forum rules
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
2017-01-06 build crashing frequently
Windows 10 64bit, AMD 8 Core, 16 GB
Nvidia GTX 670 @ 3240x1920
FreeOrion Build: Latest Windows Test Build
Nvidia GTX 670 @ 3240x1920
FreeOrion Build: Latest Windows Test Build
Re: 2017-01-06 build crashing frequently
Can anyone confirm this?
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: 2017-01-06 build crashing frequently
Probably the same weird issues that have been appearing with one of the many C++11 range based loops conversion commits.
If, as it appears from the crash report thing, a crash in the client, then presumably there is something that you're doing in the UI that causes the crash. If that can be identified, it would be easier to attempt to fix.
If, as it appears from the crash report thing, a crash in the client, then presumably there is something that you're doing in the UI that causes the crash. If that can be identified, it would be easier to attempt to fix.