[quake3-bugzilla] [Bug 5079] New: Crash with "Hunk_FreeTempMemory: bad magic"

[bugzilla-daemon at icculus.org]

https://bugzilla.icculus.org/show_bug.cgi?id=5079

           Summary: Crash with "Hunk_FreeTempMemory: bad magic"
           Product: ioquake3
           Version: SVN HEAD
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: Misc
        AssignedTo: zakk at icculus.org
        ReportedBy: blob at p0d.org
         QAContact: quake3-bugzilla at icculus.org


This bug was found while testing the current HEAD (r2080) and
is present since r2077.

Compiled for x86_64 under Linux with the following options:

make USE_CURL=1 USE_OPENAL=0 USE_CODEC_VORBIS=1 USE_MUMBLE=0 USE_VOIP=0

I started the game in single player mode after a fresh install
and it worked well (on q3dm0) but crashed while loading q3dm1
and subsequent maps.

Relevant log:

Loading vm file vm/ui.qvm...
File "vm/ui.qvm" found in "./baseq3/pak8.pk3"
VM file ui compiled to 991322 bytes of code
ui loaded in 1688544 bytes on the hunk
35 arenas parsed
32 bots parsed
Loading vm file vm/cgame.qvm...
File "vm/cgame.qvm" found in "./baseq3/pak8.pk3"
VM file cgame compiled to 1247885 bytes of code
cgame loaded in 4993536 bytes on the hunk
stitched 0 LoD cracks
...loaded 1942 faces, 113 meshes, 42 trisurfs, 0 flares
^3WARNING: Failed to load sound sound/player/announce/test.wav!
^3WARNING: could not find sound/player/announce/test.wav - using default
CL_InitCGame:  0.79 seconds
182 msec to draw all images
Com_TouchMemory: 0 msec
----- Client Shutdown (Client fatal crashed: Hunk_FreeTempMemory: bad magic) --
RE_Shutdown( 1 )
Closing SDL audio device...
SDL audio device shut down.
-----------------------
----- Server Shutdown (Server fatal crashed: Hunk_FreeTempMemory: bad magic) --
==== ShutdownGame ====
AAS shutdown.
---------------------------
Hunk_FreeTempMemory: bad magic

-- 
Configure bugmail: https://bugzilla.icculus.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.