All Projects Gameplay + OpenGL Software Renderer zdoom.org (Site)

View Issue Details

Jump to NotesIssue History
IDProjectCategoryView StatusDate SubmittedLast Update
0000594Gameplay + OpenGL[All Projects] Bugpublic2017-04-17 20:042017-04-19 03:40
ReporterMatthew the Glutton 
Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionduplicate 
PlatformDebian JessieOSOS Version
Summary0000594: [03b77c0] Memory error on exit
Description
*** Error in `/home/mchan223/doom/./gzdoom': corrupted double-linked list: 0x0000000006be84f0 ***

/home/mchan223/bin/gzdoom: line 2: 26698 Aborted                 ~/doom/./gzdoom $*
Steps To ReproduceLoad HD. https://github.com/MatthewTheGlutton/HideousDestructor/tree/372ce927ca2f96069d3b88e1885900bb9dc27f62

Warp to Map01.

Play for a while and kill at least 1 imp.

Quit.
Additional InformationHappens only on release build. No error or unusual behaviour whatsoever could be replicated with debug build.
TagsNo tags attached.

Relationships

duplicate of 0000453 closedRachael More memory error stuff 

Activities

Matthew the Glutton

Matthew the Glutton

2017-04-18 00:40

reporter   ~0001426

Better way to reproduce:

Warp to Map11
IDDQD
walk around that area coming in and out of LOS with the two imps as they attack
quit after they've launched a bunch of attacks from in and out of LOS
_mental_

_mental_

2017-04-18 05:08

developer   ~0001432

Last edited: 2017-04-18 05:09

View 2 revisions

 Callstask is similar to your previous reports:
#0  0x00007ffff6696a96 in _int_free (av=0x7ffff69dab20 <main_arena>, p=<optimized out>, 
    
have_lock=0) at malloc.c:4012
1  0x00007ffff669a98c in __GI___libc_free (mem=<optimized out>) at malloc.c:2966
2  0x0000000000794888 in ?? ()
3  0x0000000000795995 in GC::FullGC() ()
4  0x00000000008b08c9 in P_FreeLevelData() ()
5  0x00000000008b0feb in ?? ()
6  0x0000000000546842 in call_terms() ()
7  0x00007ffff6650ff8 in __run_exit_handlers (status=0, listp=0x7ffff69da5f8 <__exit_funcs>, 
   
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
8  0x00007ffff6651045 in __GI_exit (status=<optimized out>) at exit.c:104
9  0x0000000000543d8b in I_GetEvent() ()
10 0x000000000077c665 in NetUpdate() ()
11 0x000000000077eada in TryRunTics() ()
12 0x0000000000775b15 in D_DoomLoop() ()
13 0x0000000000777388 in D_DoomMain() ()
14 0x000000000052daa6 in main ()

If you want honest answer then good luck with that. Hunting optimization issues in GCC isn't the most pleasant thing to do.
I suggest you to select better compiler, the recent versions of clang are really good.
Matthew the Glutton

Matthew the Glutton

2017-04-19 00:53

reporter   ~0001454

So I just installed Clang and tried this with

cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ ..;make -j 4

and now I can no longer replicate the error...

Issue History

Date Modified Username Field Change
2017-04-17 20:04 Matthew the Glutton New Issue
2017-04-18 00:40 Matthew the Glutton Note Added: 0001426
2017-04-18 05:08 _mental_ Status new => confirmed
2017-04-18 05:08 _mental_ Note Added: 0001432
2017-04-18 05:09 _mental_ Note Edited: 0001432 View Revisions
2017-04-19 00:53 Matthew the Glutton Note Added: 0001454
2017-04-19 03:14 _mental_ Status confirmed => on hold
2017-04-19 03:40 _mental_ Relationship added duplicate of 0000453
2017-04-19 03:40 _mental_ Status on hold => closed
2017-04-19 03:40 _mental_ Resolution open => duplicate