OutOfMemory Issue - on all bastion keeps maps!!!!!!

[r3plic4tor]

these outofmemory issue happens on all bastion keeps maps .....

and it got never fixed.....


it need to be fixed the hole new diablo style depends on rifts...

this is one of the best profile but it is not 100% working cuz of these errors on this maps .

https://www.thebuddyforum.com/demon...profiles/160808-rift-bot-rifting-profile.html




View attachment 5976 2014-07-13 01.14_copie.txt

 

[iCKR]

Post an unedited version of the log please.

How To: Attach your HB-DB log file [with pictures]

 

[spaceitout]

as much as i see this error posted , i have yet to even one time encounter it ?

is it literally out of ram , or just the over-flow cause it ?

I run 16gb and have never , I mean never seen it use past 8gb with D3/DB ?

 

[r3plic4tor]

as much as i see this error posted , i have yet to even one time encounter it ?

is it literally out of ram , or just the over-flow cause it ?

I run 16gb and have never , I mean never seen it use past 8gb with D3/DB ?

I have 16 gb RAM too and it happens in rift Profile on all bastions maps

 

[r3plic4tor]

Post an unedited version of the log please.

How To: Attach your HB-DB log file [with pictures]

An unedit Version dont work with the upload seems too big any idea?

 

[r3plic4tor]

happens on all Bastion Keep maps. mostly It happens randomly and usually on the larger variations of the map.

View attachment 5976 2014-07-13 01.14 - Kopie.zip

here you are

 

[Oksehode]

as much as i see this error posted , i have yet to even one time encounter it ?

is it literally out of ram , or just the over-flow cause it ?

I run 16gb and have never , I mean never seen it use past 8gb with D3/DB ?

The program fills up with 1.3gb of memory usage in like 1-2 seconds which is the max for a 32bit application and the error spams in the DemonBuddy window.

There is clearly a memory leak somewhere and the Bastion Keep maps is triggering it randomly.

 

[iCKR]

The program fills up with 1.3gb of memory usage in like 1-2 seconds which is the max for a 32bit application and the error spams in the DemonBuddy window.

There is clearly a memory leak somewhere and the Bastion Keep maps is triggering it randomly.

I don't see any issues with your DB logs. What's your graphics/FPS settings on D3

 

[r3plic4tor]

I don't see any issues with your DB logs. What's your graphics/FPS settings on D3

I use window mode and 15 fps. But you the out of Memory issues right? And it happens only on these Type of maps

 

[mrbubbel]

I don't see any issues with your DB logs. What's your graphics/FPS settings on D3

there are System.OutOfMemoryException's thrown all over the log. look again.
as others stated several times this only happens on bastion keep maps. as a result the bot is not moving until the unstucker kicks in. sometimes the unstucker manages to "free" the character from the mapspot where System.OutOfMemoryException's are thrown. in that case it continues and will most likely get System.OutOfMemoryException's in other mapspots nearby. if the unstucker cant "free" the character it will either stuck forever or wait until it leaves the game because of gold inactivity.

at least thats my point of view. maybe its not related to mapspots in the bastion keep maps at all. maybe its some objects on the map or whatever that are causing these issues. i think it all started around db beta 407

 

[Oksehode]

there are System.OutOfMemoryException's thrown all over the log. look again.
as others stated several times this only happens on bastion keep maps. as a result the bot is not moving until the unstucker kicks in. sometimes the unstucker manages to "free" the character from the mapspot where System.OutOfMemoryException's are thrown. in that case it continues and will most likely get System.OutOfMemoryException's in other mapspots nearby. if the unstucker cant "free" the character it will either stuck forever or wait until it leaves the game because of gold inactivity.

at least thats my point of view. maybe its not related to mapspots in the bastion keep maps at all. maybe its some objects on the map or whatever that are causing these issues. i think it all started around db beta 407

That's exactly what's happening for me as well and I would guess a lot of others.

 

[r3plic4tor]

there are System.OutOfMemoryException's thrown all over the log. look again.
as others stated several times this only happens on bastion keep maps. as a result the bot is not moving until the unstucker kicks in. sometimes the unstucker manages to "free" the character from the mapspot where System.OutOfMemoryException's are thrown. in that case it continues and will most likely get System.OutOfMemoryException's in other mapspots nearby. if the unstucker cant "free" the character it will either stuck forever or wait until it leaves the game because of gold inactivity.

at least thats my point of view. maybe its not related to mapspots in the bastion keep maps at all. maybe its some objects on the map or whatever that are causing these issues. i think it all started around db beta 407

Damn right! [emoji106]

 

[Winchester]

Yup. same here.
here's my log.
View attachment 2992 2014-07-11 11.44.zip

Here's a screenshot of one of the bastion keep maps that gives the error (c/o Oksehode)

Note: Please search for OutOfMemory since the log file is huge.
That's the error, then the bot just keeps moving around the map and never finding the exit.

uploaded correct file.

 

[Oksehode]

Yup. same here.
here's my log.
View attachment 135800

Here's a screenshot of one of the bastion keep maps that gives the error (c/o Oksehode)

Note: Please search for OutOfMemory since the log file is huge.
That's the error, then the bot just keeps moving around the map and never finding the exit.

I can't find any "OutOfMemory" errors in the log file you posted.

 

[Winchester]

I can't find any "OutOfMemory" errors in the log file you posted.

uploaded correct file. lol.

thanks!

 

[r3plic4tor]

@iCKR any news? or is it not important enough?

 

[chinajade]

@iCKR any news? or is it not important enough?

Hi, R3plic4tor,

The last time I saw this, it wasn't Demonbuddy at fault. The users were running a multi-monitor manager that was chewing up all memory in certain configurations.

Let's please eliminate Demonbuddy as the source of the problem. Download and run:

RAMMap​

Go to the "Processes" tab, and sort by "Total". Toss us a screenshot that proves that it is Demonbuddy at fault.

The theory is that Demonbuddy is probably not OOM because *it* is consuming memory. Its OOM because another program has gone hog wild and is consuming it. Since Demonbuddy is a very active program its going to be the canary that detects the OOM situation first.

cheers,
chinajade

 

[r3plic4tor]

Hi, R3plic4tor,

The last time I saw this, it wasn't Demonbuddy at fault. The users were running a multi-monitor manager that was chewing up all memory in certain configurations.

Let's please eliminate Demonbuddy as the source of the problem. Download and run:

RAMMap​

Go to the "Processes" tab, and sort by "Total". Toss us a screenshot that proves that it is Demonbuddy at fault.

The theory is that Demonbuddy is probably not OOM because *it* is consuming memory. Its OOM because another program has gone hog wild and is consuming it. Since Demonbuddy is a very active program its going to be the canary that detects the OOM situation first.

cheers,
chinajade

Should i Run db and this Tool? Or only this Tool?

 

[mrbubbel]

hi. i caught it throwing System.OutOfMemoryException's today. two rammap screenshots are attached. while getting these errors it went up to ~900,000K total.

again this is the error everyone is getting:

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.List`1.set_Capacity(Int32 value)
at System.Collections.Generic.List`1.EnsureCapacity(Int32 min)
at System.Collections.Generic.List`1.Add(T item)
at Zeta.Bot.Pathfinding.PathFinder.FindPath(Point startPoint, Point endPoint, Boolean includeDiagonals, Int32 maxMilliseconds, Boolean allowPartialPaths)
at Zeta.Bot.Navigation.DefaultNavigationProvider.
(Vector3 , Boolean )
at Zeta.Bot.Navigation.DefaultNavigationProvider.GeneratePath(Vector3 destination, String destinationName, Boolean useRaycast)
at Zeta.Bot.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at Zeta.Bot.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at QuestTools.ProfileTags.ExploreDungeonTag.MoveToNextNode()
at QuestTools.ProfileTags.ExploreDungeonTag.<CreateBehavior>b__19(Object ret)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.DecoratorContinue.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.
.
()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.
()

 

[r3plic4tor]

hi. i caught it throwing System.OutOfMemoryException's today. two rammap screenshots are attached. while getting these errors it went up to ~900,000K total.

again this is the error everyone is getting:

Same for me 1300000k on heavy times...