Jump to content

Maximum Profile size crashing bot?


eeny

Recommended Posts

So i have made a quest profile thats ~ 500 steps and 500kb in size.  In quests editor it passes the 'check errors' with no probs.  however when i load it 50% of the time my bot will crash with the following .Net and application crash.  Taking a look at the .net error i assumed it was a mesh issue so i deleted all the meshes for the continent- however it came back immediately.  also cleaned out the logs folder of 900mb of logs however still having odd crashes.  Currently 2 bots will load the profile and run it, 2 are just chain crashing.  is there an issue with a maximum profile size- or do i just move down the repair install of Wrobot / .NET?

25 Jul 2016 21H35.log.html

 

 

Log Name:      Application
Source:        Application Error
Date:          25/07/2016 9:29:13 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-9CQIFVD
Description:
Faulting application name: WRobot.exe, version: 1.0.0.28188, time stamp: 0x578e2d99
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0d45b157
Faulting process id: 0x1d34
Faulting application start time: 0x01d1e667b2f7fc67
Faulting application path: C:\WRobot\WRobot.exe
Faulting module path: unknown
Report Id: 5eabbba5-43c8-41d3-b85b-ddadec0b0550
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-25T11:29:13.363226100Z" />
    <EventRecordID>3904</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-9CQIFVD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WRobot.exe</Data>
    <Data>1.0.0.28188</Data>
    <Data>578e2d99</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>0d45b157</Data>
    <Data>1d34</Data>
    <Data>01d1e667b2f7fc67</Data>
    <Data>C:\WRobot\WRobot.exe</Data>
    <Data>unknown</Data>
    <Data>5eabbba5-43c8-41d3-b85b-ddadec0b0550</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-25T11:29:13.302552900Z" />
    <EventRecordID>3903</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-9CQIFVD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: WRobot.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at &lt;Module&gt;.dtNavMesh.addTile(dtNavMesh*, Byte*, Int32, Int32, UInt64, UInt64*)
   at RDManaged.RD.AddTile(Byte[])
   at wManager.Wow.Helpers.PathFinderClass.Pather.LoadTile(Int32, Int32)
   at wManager.Wow.Helpers.PathFinderClass.Pather.LoadAround(robotManager.Helpful.Vector3)
   at wManager.Wow.Helpers.PathFinderClass.Pather.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3, Boolean ByRef, Boolean ByRef, Int32, Single, Boolean)
   at wManager.Wow.Helpers.PathFinder.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3, System.String, Boolean ByRef, Boolean, Boolean)
   at wManager.Wow.Helpers.PathFinder.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3, System.String)
   at wManager.Wow.Helpers.PathFinder.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3)
   at wManager.Wow.Class.QuestGrinderClass.Pulse()
   at wManager.Wow.Class.QuestsSorted.Run()
   at Quester.Bot.Ewiqaileitega.Run()
   at robotManager.FiniteStateMachine.Engine.Baura(robotManager.FiniteStateMachine.State)
   at robotManager.FiniteStateMachine.Engine.Pulse()
   at robotManager.FiniteStateMachine.Engine.Axuca(System.Object)
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)

</Data>
  </EventData>
</Event>

Link to comment
Share on other sites

Exception info talks about pathfinder issue. It says access violation issue then it says addtile is failing so seems like the issue is a file being read only or otherwise corrupt... 

 

Try moving the bot to another location since currently it is at c:/wrobot and usually begining of C is read only or somehow otherwise windows screwing you over 

Link to comment
Share on other sites

Its all over Kalimdor.  One bots failing in StoneTalon mountains, another in Valley of trials.  initially i thought meshes were the problem because i saw one log file crash trying to load one, so i deleted all the kalimdor meshes and it still crashed.

 

Im installing a new SSD later today.  il put a fresh install of wrobot on that and see where i land

Link to comment
Share on other sites

Fresh install of wrobot on the new SSD (G:/Wrobot).. all working fine at this time.... shrugs 

 

Same OS, same profiles no crash.  The old install has been running pretty hard for a few months.. maybe something just got messed up

Link to comment
Share on other sites

3 minutes ago, eeny said:

Fresh install of wrobot on the new SSD (G:/Wrobot).. all working fine at this time.... shrugs 

 

Same OS, same profiles no crash.  The old install has been running pretty hard for a few months.. maybe something just got messed up

Let me guess, windows 10? :biggrin:

Link to comment
Share on other sites

Just now, eeny said:

Its actually Arch Linux.....jk  of course its Win10 =P

Nice, i use Kali linux. :biggrin:

But now for real, putting stuff directly into C:\  with Windows 10, can cause several permission problems. ( writing and such )

Link to comment
Share on other sites

9 minutes ago, Runaro said:

Nice, i use Kali linux. :biggrin:

But now for real, putting stuff directly into C:\  with Windows 10, can cause several permission problems. ( writing and such )

Today i learneded something

Wiggum.jpg

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...