[1.3.0][Duke Nukem 3D] Game crash on opening textured map

[3saster]

Steps to reproduce: Load the save file (for E4L1) and immediately press tab twice to open the textured automap. The game immediately crashes with the error

Code: Select all

bad array new length

I'm unfortunately unable to reproduce this now for some reason, but it was consistently crashing on opening the textured automap before, but not anymore. mjr was able to reproduce this too, so I don't know what's going on.

EDIT: Seems it can still be reproduced consistently. Run around a bit while repeatedly opening and closing the automap. Eventually when the textured automap is opened it will crash.

[Graf Zahl]

Makes me wonder if this is related: https://github.com/coelckers/Raze/issues/595
That little oversight has produced quite a bit of problems and will be enough to do a quick point release.
So I'd appreciate if you could check once a devbuild or CI artifact becomes avaiable.

[mallo]

I just checked and the issue still happens on the newest build.

[3saster]

So I'd appreciate if you could check once a devbuild or CI artifact becomes avaiable.

Tried the 64-bit release build of the CI artifact of commit 014c6bb3b231da3d8fcd8262185ecbf3c059b217, but it wouldn't let me load the save as it's from a different version, and unfortunately this is so esoteric I can't reliably produce another save like this. Is there a way to force loading a save in Raze?

[Graf Zahl]

That artifact is from the work branch which is not savegame compatible. In that case better wait for the next devbuild.

[3saster]

Quick test of current devbuild 10c6fde8d still crashes when opening the textured automap. I noticed two things on this build though:
1. It crashes immediately on opening the textured automap. On 1.3.0 I would need to move around a bit and open the map multiple times before it would crash sometimes. On 1.3.0 though it would initially crash immediately everytime though, then when I tried it again an hour later I had to do the movement stuff, so it could be the same thing happening.
2. The game crashes if I approach the hallway to the left of the save start. This also happens on 1.3.0, and it seems I didn't notice that when making the report yesterday.

The commits on master that are not included in the current devbuild are GLES related commits, so it should have no bearing on this bug. Is there a different commit you had in mind for testing?

[Graf Zahl]

Never mind, I found the cause in the mean time:

https://github.com/coelckers/Raze/commi ... 35b46ac312