JSON-related crash
issueid=4258 01-31-2016 11:20 PM
Junior Member
Number of reported issues by cataplexy: 2
JSON-related crash

I've been getting a game-ending crash with R65 pretty frequently. A text box pops up with "Expected chunk 'JSON' not found." and the game crashes. It seems like it usually occurs when switching rooms (saving?). Loading the resultant savegame then gives the same error. I've attached an affected savegame.
Issue Details
Issue Number 4258
Project ADOM (Ancient Domains Of Mystery)
Category All without NotEye
Status Fixed
Priority 1 - Highest
Affected Version ADOM r65 (v2.1.0)
Fixed Version ADOM r66 (v2.2.0)
Milestone Potential work pipeline
Users able to reproduce bug 8
Users unable to reproduce bug 0
Assigned Users adom-admin, jt
Tags (none)




02-01-2016 02:56 AM
Junior Member
I may be wrong, but after a bit more investigation, my impression is that this has to do with the "shifting dungeons" room - as if the game doesn't save it properly?

02-01-2016 11:31 PM
The Creator
I do have a set of shifting room save files that all work.

The save file provided looks corrupted in some way but I yet have no idea what exact type of corruption that might be. Did anything else happen before you saved this?

The message you see about an expected chunk not being found can only occur when you are trying to load a game. Is this game a game you saved on a shifting dungeon level? Or is it a backup from some other crash?

02-01-2016 11:55 PM
added another savefile going with the JSON crash trying to load D:3 from D:2 (a shifting dungeon level)

is it supposed to be like a rockslide?

I tested the boundaries and it looped me to the top through it, if that has anything to do with it

02-02-2016 12:17 AM
Member
This happened when one of my chars was descending a dungeon level in the Unremarkable Dungeon. Can't remember which level... the game crashes again immediately when you try and reload it from backup, anyway.
I've attached the .bak and .err files generated.
This was on Windows 10.

02-02-2016 01:02 AM
Junior Member
All the games it's happened on were normal except for the crash. The message does indeed pop up in-game - causing a crash - and then again when trying to load the resultant save file.

Also - in one game (not the attached save) I saved and quit normally on a shifting dungeons level (no crash), then loaded the same file immediately, and it gave the same error.

02-03-2016 08:21 AM
Senior Member
Just happened to me, decending to UD: 6. I got the 'you sense the forces of the nether approaching' message, followed by [saving backup copy rolf.bak. please stand by.] and the expected chunk JSON message. Reloading causes an instant crash.

02-04-2016 08:17 PM
Ancient Member
Quite sad. Had a fun character just get the crash after being in a shifting level. Seems like the game is having trouble saving shifting levels?

02-05-2016 09:59 AM
Senior Member
This is the reason it might be a good idea to keep not one, but two last save games, in case something breaks in the saving process.

02-05-2016 02:33 PM
Ancient Member
That's a good idea! You should submit an rfe for that, it would greatly smooth out the prerelease phase.

02-11-2016 08:37 PM
Ancient Member
I just had this happen. Had been in a shifting room area maybe 100 turns earlier. Save won't load at all.

02-12-2016 03:33 AM
Ancient Member
ditto. Had a bard with perfect skill rolls too :(

03-24-2016 06:56 AM
Ancient Member
so uh i like the R65 version this going to get fixed? :)

05-10-2016 06:44 AM
It looks like this is still an issue, as of the newest version of the game (r65). I've had several saves corrupt already due to this, usually from autosaves when switching floors from a floor with a shifting room.

Is it being worked on at all?

05-10-2016 07:22 PM
Senior Member
Quote Originally Posted by daft inquisitor
It looks like this is still an issue, as of the newest version of the game (r65). I've had several saves corrupt already due to this, usually from autosaves when switching floors from a floor with a shifting room.

Is it being worked on at all?
r65 is the first release where this was a problem and there hasn't been any newer versions since so it makes sense that this would be a problem in your games on that version. I'm pretty sure The Creator is still working on this and several other bugs that were introduced in r65.

05-11-2016 03:07 AM
Ah, gotcha. I was under the impression this was reported during r64, due to the way some of the above comments were worded.

05-11-2016 12:16 PM
Senior Member
Quote Originally Posted by daft inquisitor
Ah, gotcha. I was under the impression this was reported during r64, due to the way some of the above comments were worded.
Yeah, it does kind of seem that way but if you look at the bug report description to the right it says it was reported in r65, just a tip for the future. I'm hoping this does get fixed soonish because r65 brings in some cool interesting stuff.

06-12-2016 10:06 PM
The Creator
I have rewritten some part of the internal code that might be responsible for it without seeing any actual problem. But sometimes rewriting helps. Though currently we still are confused.

06-15-2016 06:37 AM
The Creator
I have removed the sources for inconsistencies. Now things should be stable.

+ Reply