Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #1468  -  Shooting with the bow implementation crashes the game
Posted Jun 15, 2020 - updated Jul 09, 2020   Shortlink: http://arx.vg/1468
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
    Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    RESOLVED
  • Priority
    Not determined
  • Reproducability
    Always
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
I was in the goblin kingdom training the aim with the bow and the game crashed, using the latest snapshot, when you shoot arrows this crash appears, maybe this is helful:

Assertion Failed at Trail.cpp:117: m_positions.size() >= size_t(std::ceil(n)) + 2

Unhandled exception

Exception code: BREAKPOINT 

 Instruction address: 0x7ff6e37f100e
 Stack pointer: 0x7b33cecc0


Callstack: 
 arx.exe!0x7ff6e37f100e
 arx.exe!0x7ff6e38b1fd5
 arx.exe!0x7ff6e3778995
 arx.exe!0x7ff6e3779956
 arx.exe!0x7ff6e37760d2
 arx.exe!0x7ff6e3787cfe
 arx.exe!0x7ff6e387f01a
 arx.exe!FT_GlyphSlot_Own_Bitmap()
 KERNEL32.DLL!BaseThreadInitThunk()
 ntdll.dll!RtlUserThreadStart()


Steps to reproduce this issue
Aim and shoot with the bow multiple times

#1
icon_reply.pngReply
Comment posted by
Guest user
Jun 15, 21:40
Also, try to use Speed speel too. Same problem.
#2
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jun 15, 21:55
Yeah, speed spell and arrow trails use the same effect. I have not been able to reproduce the crash yet though - not sure why it's failing for some but not for me.
#3
icon_reply.pngReply
Comment posted by
Guest user
Jun 16, 04:40
Try to use MAX cheat magic. For me, if i use MAX - 100% chanse to crash.
#4
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jun 20, 05:30
Still have not been able to reproduce the assert failure. Can you please run https://arx-libertatis.org/files/misc/arx-libertatis-1.2-trailtest/arx-libertatis-1.2-trailtest-windows.zip and upload arx.log after it crashes.
#5
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jun 27, 19:50
Hi, if anyone who runs into this could run https://arx-libertatis.org/files/snapshots/arx-libertatis-1.2-trailtest/ and then post the arx.log file after it crashes that would help narrow this down.
#6
icon_reply.pngReply
Comment posted by
Kender
Jun 28, 07:52
I tried the "Arx Libertatis 1.2-trailtest + e081737" build but it does not crash.

With the "Arx Libertatis 1.2-dev-2020-06-14 + 2a0af63" build it crashes 100%

Edit: many hours playing later the trailtest build still has not crashed. The arx.log gets a bit big with all the trail logging though smileys/2.png

Looks like something changed between the two builds other than the additional debug logging. Which might explain why you could not reproduce it?

I just tried the dev snapshot again and that reliably crashes when an Ylside casts Speed.

#8
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jul 05, 18:21
Hopefully fixed in the latest development snapshot - please verify.

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.
#9
icon_reply.pngReply
Comment posted by
Guest user
icon_reply.pngJul 09, 21:53, in reply to comment #8
I was having the same crash when first fighting the Ysildes and the latest snapshot seems to have fixed the assertion error.

Daniel Scharrer wrote:
Hopefully fixed in the latest development snapshot - please verify.

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.