Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #874  -  [5508C599] arx.exe!ARX_SCRIPT_Timer_Check() [script.cpp:1841]
Posted Aug 03, 2016 - updated Jun 25, 2017   Shortlink: http://arx.vg/874
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Crash report
  • Status
     
    Fixed
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     CrashBot
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    RESOLVED
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Windows
  • Architecture
    icon_customdatatype.png amd64
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
Assertion Failed at Script.cpp:1841: st->start <= now

Unhandled exception

Exception code: BREAKPOINT

 Instruction address: 0x1401f83f5
 Stack pointer: 0x14f670


Callstack:
 arx.exe!0x1401f83f5
 arx.exe!0x1400b0ffb
 arx.exe!0x1400b1f85
 arx.exe!0x1400af31c
 arx.exe!0x1400aee9e
 arx.exe!0x1400b79e0
 arx.exe!0x1400bf589
 arx.exe!0x1401bcac2
 arx.exe!0x1402ab9b5
 KERNEL32.DLL!BaseThreadInitThunk()
 ntdll.dll!RtlUserThreadStart()
Symbols:
 0  arx.exe!ARX_SCRIPT_Timer_Check() [script.cpp : 1841 + 0x1e]
 1  arx.exe!ArxGame::updateLevel() [arxgame.cpp : 1869 + 0x0]
 2  arx.exe!ArxGame::render() [arxgame.cpp : 2228 + 0x0]
 3  arx.exe!ArxGame::doFrame() [arxgame.cpp : 1334 + 0x0]
 4  arx.exe!ArxGame::run() [arxgame.cpp : 1259 + 0x0]
 5  arx.exe!runGame() [core.cpp : 293 + 0x0]
 6  arx.exe!utf8_main(int,char * * const) [startup.cpp : 207 + 0x0]
 7  arx.exe!WinMain [windowsmaingui.cpp : 48 + 0xe]
 8  arx.exe!__tmainCRTStartup [crtexe.c : 618 + 0x15]
Steps to reproduce this issue
Nothing entered.

#1
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 03, 18:59
A file was uploaded. arx.logicon_open_new.png This comment was attached:

arxcrash-9024-936570064
#3
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 03, 18:59
A file was uploaded. cfg.iniicon_open_new.png This comment was attached:

arxcrash-9024-936570064
#4
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 03, 18:59
A file was uploaded. crash.dmpicon_open_new.png This comment was attached:

arxcrash-9024-936570064
#5
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 03, 18:59
A file was uploaded. crash.txticon_open_new.png This comment was attached:

arxcrash-9024-936570064
#6
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Aug 03, 20:03
Hi,

do you remember what you were doing when the game crashed?

Can you reproduce the crash?
#8
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 05, 00:48
After leaving the Akbaa temple the game crashed
#9
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 05, 00:48
A file was uploaded. arx.logicon_open_new.png This comment was attached:

arxcrash-1676-3420007277
#10
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 05, 00:48
A file was uploaded. cfg.iniicon_open_new.png This comment was attached:

arxcrash-1676-3420007277
#11
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 05, 00:48
A file was uploaded. crash.dmpicon_open_new.png This comment was attached:

arxcrash-1676-3420007277
#12
icon_reply.pngReply
Comment posted by
 CrashBot
Aug 05, 00:48
A file was uploaded. crash.txticon_open_new.png This comment was attached:

arxcrash-1676-3420007277
#17
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Sep 29, 09:19
Possibly fixed in the 1.2-dev-2016-09-23 development snapshot.
#18
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Jun 25, 12:45
Marking this as fixed since there are no reports with version 1.2-dev-2016-09-23 or later.

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Fixed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • This issue's progression has been updated to 100 percent completed.