Dungeon Crawl Stone Soup Tracker - DCSS
Viewing Issue Advanced Details
10288 Bug Report crash always 2016-02-18 07:04 2016-02-18 16:22
aleksil Local  
neil Windows  
normal Tiles  
resolved 0.18 ancient branch  
0.18-a0-1347-gb9e2fb4 done  
none    
none 0.18 ancient branch  
0010288: Game keeps crashing with an in-progress character.
After installing the latest trunk update, I've been experiencing a number of crashes with an in-progress character. It happens intermittently when exiting a screen (at least % and some help screens) and saving a character. A fresh character seemed to be unaffected.
? file icon Roll.cs [^] (671,247 bytes) 2016-02-18 07:04
txt file icon crash-Roll-20160218-080048.txt [^] (44,460 bytes) 2016-02-18 07:05 [Show Content]
txt file icon crash-Roll-20160218-093955.txt [^] (51,167 bytes) 2016-02-18 15:57 [Show Content]
txt file icon grind.txt [^] (9,724 bytes) 2016-02-18 16:02 [Show Content]
Issue History
2016-02-18 07:04 aleksil New Issue
2016-02-18 07:04 aleksil File Added: Roll.cs
2016-02-18 07:05 aleksil File Added: crash-Roll-20160218-080048.txt
2016-02-18 07:07 aleksil Note Added: 0030200
2016-02-18 15:57 neil File Added: crash-Roll-20160218-093955.txt
2016-02-18 15:57 neil Note Added: 0030202
2016-02-18 16:00 neil File Added: grind.log
2016-02-18 16:00 neil Note Edited: 0030202
2016-02-18 16:02 neil File Deleted: grind.log
2016-02-18 16:02 neil File Added: grind.txt
2016-02-18 16:12 neil Note Edited: 0030202
2016-02-18 16:22 neil Note Added: 0030203
2016-02-18 16:22 neil Status new => resolved
2016-02-18 16:22 neil Fixed in Branch => 0.18 development branch
2016-02-18 16:22 neil Resolution open => done
2016-02-18 16:22 neil Assigned To => neil

Notes
(0030200)
aleksil   
2016-02-18 07:07   
Update: Seems like there are crash reports from the new character, too. I didn't notice at first as they seem to happen while saving and exiting.
(0030202)
neil   
2016-02-18 15:57   
(edited on: 2016-02-18 16:12)
Second crashlog generated from the same save, under Linux so there's a backtrace.

And a valgrind log—the memory corruption on doing %% was lucky enough to crash valgrind, but there is still useful log before that point.

Ignore the first valgrind error (invalid read of size 1) here: it's a pre-existing problem that appears to be unrelated.

(0030203)
neil   
2016-02-18 16:22   
Fixed in trunk (0.18-a0-1352-g62dae19), thanks!