kohakulee / corsix-th

Automatically exported from code.google.com/p/corsix-th
0 stars 0 forks source link

Crash on moving staff member #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Occasionally when grabbing a staff member game crashes with following log:

An error has occured while running the timer handler.
A stack trace is included below, and the handler has been disconnected.
Lua\humanoid.lua:132: Empty action queue
stack traceback:
        [C]: in function 'assert'
        Lua\humanoid.lua:132: in function 'Humanoid_startAction'
        Lua\humanoid.lua:216: in function 'timer_function'
        Lua\entity.lua:94: in function 'tick'
        Lua\staff.lua:29: in function 'tick'
        Lua\world.lua:273: in function 'onTick'
        Lua\app.lua:308: in function 'dispatch'
        Lua\app.lua:261: in function <Lua\app.lua:256>

Warning: No event handler for timer
An error has occured while running the buttonup handler.
A stack trace is included below, and the handler has been disconnected.
Lua\dialogs\place_staff.lua:53: attempt to index field '?' (a nil value)
stack traceback:
        Lua\dialogs\place_staff.lua:53: in function 'close'
        Lua\dialogs\place_staff.lua:97: in function 'onMouseUp'
        Lua\window.lua:238: in function 'onMouseUp'
        Lua\ui.lua:397: in function 'dispatch'
        Lua\app.lua:261: in function <Lua\app.lua:256>

Tends to happen when grabbing doctor while there is an unoccupied room they
could be in.

Original issue reported on code.google.com by chris_lo...@hotmail.com on 7 Dec 2009 at 3:05

GoogleCodeExporter commented 9 years ago
I believe to have found the cause of this issue. If I'm correct, it happens when
picking up a staff that is currently on a temporary idle action (caused by 
meander
action). The assert happens when the timer kicks in that is supposed to end the 
idle
action.

Original comment by roujin.mw on 7 Dec 2009 at 3:34

GoogleCodeExporter commented 9 years ago
That does sound like a plausible explanation. As long as there's not something 
else
going on, r157 should fix this.

Original comment by cor...@gmail.com on 7 Dec 2009 at 1:41