r3274 Console warning on quitting the game.

[Enjay]

Whenever I play a game, when I quit, the following message is sent to the console:

Code: Select all

Warning: 'Object' is freed outside the GC process.

To replicate, start a game with a log file running, enter the first map then quit. The above line should be at the end of your log file. Happens to me every time in Zdoom and GZdoom and in any of the supported games. It doesn't seem to have a detrimental effect, but it's there, so I reported it.

[Edward-san]

Do you mean running it like this:

Code: Select all

zdoom +logfile foo.log

?
In that case I cannot reproduce this in linux Ubuntu 10.10 x86-64 release and debug, r3274. The last message in console is this:

Code: Select all

+MAP01 - entryway

Also, can you reproduce this in r3271 and below?

[Enjay]

Do you mean running it like this:

Yes.

Full log

---

Code: Select all

Log started: Tue Jul 26 23:04:35 2011

W_Init: Init WADfiles.
 adding C:/Doom/zdoomSVN/zdoom.pk3, 547 lumps
 adding C:/Doom/gzdoom/doom2.wad, 2951 lumps
I_Init: Setting up machine state.
CPU Speed: 2673 MHz
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
  Family 6, Model 26, Stepping 4
  Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
I_InitSound: Initializing FMOD
FMOD Sound System, copyright © Firelight Technologies Pty, Ltd., 1994-2009.
Loaded FMOD version 4.26.10
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
G_ParseMapInfo: Load map definitions.
S_InitData: Load sound definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading default status bar definition.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
I_InitInput
I_StartupMouse
I_StartupKeyboard
I_StartupXInput
I_StartupRawPS2
I_StartupDirectInputJoystick
Resolution: 1920 x 1200
16 bots read from bots.cfg



MAP01 - entryway

ACS scripts unloaded.
Warning: 'Object' is freed outside the GC process.

Also, can you reproduce this in r3271 and below?

Of the revisions that I have quick access to, r3263 shows this behaviour but r3249 does not. So the change that caused this happened sometime between those two revisions.

[Edward-san]

Two lines are interesting:

Code: Select all

16 bots read from bots.cfg

and

Code: Select all

ACS scripts unloaded.

I don't have these ones. What happens if you don't use bots?

That warning message is displayed in the destructor of the DObject class:

Code: Select all

		if (!(ObjectFlags & OF_YesReallyDelete))

		{

			Printf ("Warning: '%s' is freed outside the GC process.\n",

				type != NULL ? type->TypeName.GetChars() : "==some object==");

		}

I checked the changes on the file dobject.cpp, an this has only a new include in r3259:

Code: Select all

#include "farchive.h"

And in dobject.h this is added (r3263):

Code: Select all

	// For cleanup

	void DelSoftRootHead();

[Enjay]

Two lines are interesting:

Code: Select all

16 bots read from bots.cfg

and

Code: Select all

ACS scripts unloaded.

The first line is normal if you have a bots.cfg file in a zcajun sub folder of Zdoom. It does not mean that I am using bots, merely that Zdoom has loaded the definitions for 16 bots from the file. Removing my zcajun folder removes the "16 bots" message but does not change the "GC process" message.

The "ACS scripts unloaded" is a message that you get if the map is question is in ZdoomHexen format but does not have any scripts. Specifically, in this case, my Doom2 IWAD has been run through ZWADCONV for editing purposes. However, using an unaltered IWAD still gives the "GC process" message.

[Kappes Buur]

For me

Warning: 'Object' is freed outside the GC process.

first happens with

GZDoom 1221 2011-07-06 12:47:47 gez /trunk/ * Updated to ZDoom r3249:

[Gez]

Funnily enough, I don't get that bug in GZDoom r1224 or earlier... It appears in r1225 for me.

Checking the corresponding ZDoom versions, I get the expected results: there's no such warning message in r3262; which is the version that corresponds to GZDoom r1224; but the warning message does appear in r3263, which corresponds to GZDoom r1225.


Fixed in GZDoom.