ZDoomZ + Final Doom = Hard Reset?

[mindfield]

Now, I don't know if it's UDMH or something else, but something's going wonky with ZDoomZ.

For starters, I'm playing on a Zire72 with UDMH 3.0 and anywhere between 10 and 13.5 megs free main memory, fully defragged (initially by intention, but later against my will -- more below)

Doom II: Played fine beginning to end.
Doom: Plutonia: Loaded save game from E1L3, near the beginning, crashes -- hard reset. It did this consistently, at the same place, every time.
Doom: TNT (Evilution): E1L5, crashed in control room near the beginning, after obtaining the blue key. Again, pressing the reset pin forced a hard reset and a full restore was necessary.

Now, I'm not running much in the way of DAs/Hacks -- Fonts4OS5 (enabled only for one app) and UDMH are the only things constantly running.

Is it possible it's just trying to steal more available RAM (via UDMH) than I have, thus overwriting existing memory and forcing the hard reset? When it first happened I was running with about 10 free megs, so afterwards I cleared some space, but it happened again, in the same place. What's more is that I'd been past the crash point before (though not as far in the game in terms of having killed creatures/acquired keys) so it just seems odd that it would pick that point to consistently crash at.

Would this be a ZDoomZ thing or a UDMH thing? (If it's the latter I could go bug Dmitry about it)

[hawkeyefile]

this does not happen on my TE.

[srraziel]

I had the same problem on my Zire 72, running Doom 64 WAD files, when i'm just walking on the stage a error message appears and my palm hard reset immediatly. This gave me a lot of trouble cause i didn't backed up my device lately, now i'm always afraid to play with wads files. I don't know if this problem only happens on zire 72 devices, i just hav problems with timidity too... It would be nice if someone could fix those bugs... and if someone's insterested, i'm free for testing any modifications on the programs...

thanks.

[metaview]

The bad thing is, one developer needs to reproduce the bug on its own. Then he can try to catch and fix it. It isn't difficult but very, very time consuming. Most of the times, there are buffers too small or misaligned memory accesses. This sometimes can show up and sometimes will be hidden, depending on the device, the memory layout and stuff. So I'm very sorry, I don't have any reproducable bug with ZDoomZ on one of my devices. That's why I can't help. If the wad's are free, you could give a link to the wad, maybe post a save game near the the crash place and if I find the time I will at least try to reproduce it and if it works I may fix it.

Regards
Henk