Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #843  -  [81683FDF] arx.exe!0x1401e58be
Posted May 19, 2016 - updated Apr 09, 2017   Shortlink: http://arx.vg/843
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 Arx Libertatis 1.2-dev
Issue description
Illegal storage access

Exception code: ACCESS_VIOLATION

 Instruction address: 0x1401e58be
 Memory accessed: 0x3822acc90
 Stack pointer: 0x12f8f0


Callstack:
 arx.exe!0x1401e58be
 arx.exe!0x14017e1f4
 arx.exe!0x14014e053
 arx.exe!0x1400a9939
 arx.exe!0x1400a9fa9
 arx.exe!0x1400a725e
 arx.exe!0x1400af710
 arx.exe!0x1400b6b64
 arx.exe!0x1401adef2
 arx.exe!0x140276ed5
 kernel32.dll!BaseThreadInitThunk()
 ntdll.dll!RtlUserThreadStart()


Symbols:
 0  arx.exe!SendIOScriptEvent(Entity *,ScriptMessage,std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &) [script.cpp : 1604 + 0xf]
 1  arx.exe!SecondaryInventoryHud::update() [secondaryinventory.cpp : 155 + 0x5d]
 2  arx.exe!HudRoot::draw() [hud.cpp : 1484 + 0x0]
 3  arx.exe!ArxGame::renderLevel() [arxgame.cpp : 2063 + 0x0]
 4  arx.exe!ArxGame::render() [arxgame.cpp : 2225 + 0x0]
 5  arx.exe!ArxGame::run() [arxgame.cpp : 1259 + 0x0]
 6  arx.exe!runGame() [core.cpp : 291 + 0x0]
 7  arx.exe!utf8_main(int,char * * const) [startup.cpp : 207 + 0x0]
 8  arx.exe!WinMain [windowsmaingui.cpp : 48 + 0xe]
 9  arx.exe!__tmainCRTStartup [crtexe.c : 618 + 0x15]
Steps to reproduce this issue
I tried to search fallen goblin and it's crashed

#3
icon_reply.pngReply
Comment posted by
 CrashBot
May 19, 15:42
A file was uploaded. cfg.iniicon_open_new.png This comment was attached:

arxcrash-4124-3059050982
#1
icon_reply.pngReply
Comment posted by
 CrashBot
May 19, 15:42
A file was uploaded. arx.logicon_open_new.png This comment was attached:

arxcrash-4124-3059050982
#4
icon_reply.pngReply
Comment posted by
 CrashBot
May 19, 15:42
A file was uploaded. crash.dmpicon_open_new.png This comment was attached:

arxcrash-4124-3059050982
#5
icon_reply.pngReply
Comment posted by
 CrashBot
May 19, 15:42
A file was uploaded. crash.txticon_open_new.png This comment was attached:

arxcrash-4124-3059050982
#7
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
May 19, 19:17
Not sure what's up with the path and script encoding…

Did Arx Libertatis work previously for you with the same data files? If so, which version?
#11
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
May 19, 22:35
I've committed a fix for the crash and the filesystem path encoding, however there is still the underlying issue with the script error. Will look into why the variable type char is different later.
#12
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Apr 09, 15:22
The crash should be fixed.

As for the script variable errors, I don't think there is anything we can do here without having access to the scripts in question. If they come from and official Arx Fatalis distribution, please let us know so that we can add support for that variant.

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.