Help Client Insufficient Memory Problem

[ERROR501]

Hello, I need help for this problem
struggling to fix this problem for a week but don't find a solution.

 

My client have memory leak problem when player reach 100 at the same place
already removed all unecessary interface and custom equipment but the problem is still there

 

does anybody know how to solve this?

 

 

 

[AlmostGood]

all these errors say is that mem allocation failed, prolly due hitting 32bit limits. Call history wont provide any useful data in this case, because its just consequence of leak somewhere else. I would revert all client changes to clean system with just own .dats and go from there in small increments at time, monitoring crashes.

[`Son]

Are you using the retail interface?

[ERROR501]

  On 8/22/2021 at 8:24 PM, AlmostGood said:

all these errors say is that mem allocation failed, prolly due hitting 32bit limits. Call history wont provide any useful data in this case, because its just consequence of leak somewhere else. I would revert all client changes to clean system with just own .dats and go from there in small increments at time, monitoring crashes.

Expand  

So you saying this is .dat problem? Meaning that I need more clean system?

  On 8/22/2021 at 9:14 PM, `Son said:

Are you using the retail interface?

Expand  

I have custom interface but already removed and the problem is still there

[Xtellia]

Depend on how much custom data is loaded. Client crashes if more than 1.8GB ram is used.

[ERROR501]

  On 8/23/2021 at 5:56 AM, Xtellia said:

Depend on how much custom data is loaded. Client crashes if more than 1.8GB ram is used.

Expand  

what you saying if we have too many custom files it will causing client crash?

[BruT]

as i can see this is more like a community board error

the second error for me is more like an unverified/incorrect client files

Edited August 23, 2021 by BruT

[ERROR501]

  On 8/23/2021 at 7:51 AM, BruT said:

as i can see this is more like a community board error

Expand  

how come? client crash not happened when players opened community board, it happened when so many players doing mass war, FPS will be drop and everything will be more like heavy and suddenly crashed happen

[NevesOma]

  On 8/23/2021 at 7:51 AM, BruT said:

as i can see this is more like a community board error

the second error for me is more like an unverified/incorrect client files

Expand  

e_u842_starfall_green it's an Emitter ( let's say effect ) from the default  LineageEffect.u package.

The problem is a bit different.

[BruT]

  On 8/23/2021 at 8:06 AM, NevesOma said:

e_u842_starfall_green it's an Emitter ( let's say effect ) from the default  LineageEffect.u package.

The problem is a bit different.

Expand  

the first error is from cb

[NevesOma]

  On 8/23/2021 at 8:46 AM, BruT said:

the first error is from cb

Expand  

Ofc. It is logical to assume that my answer refers to your second answer about effect and not your first about CB.

[AlmostGood]

you can safely ignore what crash state when its about hitting 2gb limit - it will just crash at exact moment where any action in game requested new alloc and reached limit, even when given action didn't contribute to root problem at all.

It can be any change in client or malformed packet, also make sure server properly removes all ingame objects when out of range

[ERROR501]

  On 8/23/2021 at 12:29 PM, AlmostGood said:

you can safely ignore what crash state when its about hitting 2gb limit - it will just crash at exact moment where any action in game requested new alloc and reached limit, even when given action didn't contribute to root problem at all.

It can be any change in client or malformed packet, also make sure server properly removes all ingame objects when out of range

Expand  

I agree, maybe I can start from remove or decrease ingame objects when out range

[AlisaCodeDragon]

1 ) use a clean patch

2 ) check whether support for more than 2 gigabytes is enabled

 

it is better to use a clean system patch

[ERROR501]

  On 8/23/2021 at 2:38 PM, AlisaCodeDragon said:

1 ) use a clean patch

2 ) check whether support for more than 2 gigabytes is enabled

 

it is better to use a clean system patch

Expand  

Thank you alisa! I will test this