Crashes about integer overflow, out-of-range values, getting wrong position for polymorphed/teleported/displaced entities (or limbs), or wrong initialization order?

[jakwings]

The title says it all. I suspect most of the crashes I got are caused by them and I keep fighting crashes on the weekends.

Some logs will come later in case anyone has similar issues.

The notable ones are:

• Main/Source/igraph.cpp:247 bitmap* Bitmap = RawBitmap->Colorize(...) references freed memory of a temporary variable during Main/Source/igraph.cpp:110 Graphic[c] = new bitmap(...).
• game::TryTravel(...) and then Square->GetPos() while going upstaris/downstairs.

It happens very often, so next time I will attach my saves here.

If you have similar crashes, logs or any clues, please share!

[AquariusPower]

could you drop a stacktrace too? and if you can enable the dbgmsg (if it is not encumbering) it may help too, to drop also the last 100 lines before the stacktrace of the crash happens, but may not be necessary.

going up or down means:

• player is removed from current level
• current level is saved w/o player
• travelTo level is loaded or created (crashes usually happen here, actually only saw while a new level is being created. loading is ok)
• player is placed on the travelTo level

I always run it like nice -n 19 cgexec -g memory:groupMem500MB nemiver ivan even when I am just having fun (mmm... but I have fun coding too so...)