[http://sourceforge.net/p/ufoai/bugs/2065 Item 2065] imported from sourceforge.net tracker on 2013-01-28 19:18:54

The game crash on an assert m_node_container.c line 473 "assert(item->t)". Item (object on the right hand of a soldier) is non null but have a null type.


===== Comments Ported from Sourceforge =====

====== bayo-fr (2009-02-22 15:32:49) ======

it can be a problem with initialisation of menuInventory (global var), or a missing test into the the container node
====== geever (2009-02-28 19:32:46) ======

savegame
====== geever (2009-02-28 19:32:47) ======

I found a bug, should be related.

Load the attached savegame, send the Firebird to the crash site, select "Enter" battle. The game will drop you back with "Impossible to assemble...". Now select the Firebird, send it home. Open the base/aircraft/soldiers/equip soldiers. The game crashes with SEGFAULT.

-geever
File Added: save3.zip
====== geever (2009-02-28 19:34:11) ======

File Added: backtrace
====== bayo-fr (2009-02-28 21:18:54) ======

I just test the geever savegame. With Window_debug.

The game dont crash but the base inventory is empty.

Then it can come from an uninitialized data.
====== bayo-fr (2009-02-28 21:36:51) ======

Sorry. My last comment is wrong. I can't reproduce the bug. The "empty" container come from my current video mode (widescreen test). I redo the same thing, and every thing work.
====== geever (2009-02-28 22:39:58) ======

It doesn't crash if I save and reload after the mission. Must be some memory corruption in soldier equipment stuff...

ps. We should really give the items to soldiers...

-geever
====== tlh2000 (2009-03-01 13:01:51) ======

the problem is that menuInventory is not reset - settings menuInventory to NULL in e.g. LE_Cleanup() fixes this - but there should be a better solution as setting a global var from another place where it doesn't belong.
====== tlh2000 (2009-03-01 14:39:06) ======

might be fixed in r23206
====== sf-robot (2009-03-18 18:57:11) ======

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).