Skryp _ LotzoTheUltraBear

Question about tbb4Malloc_bi

12 posts in this topic

Hello dudes,

one question about the malloc Startingparameter.

  1. First i have insert "-malloc=system" which is using the malloc of the system, right?
  2. Then i tried "-malloc=tbbmalloc" with the .dll file in the main folder and the server started fine.
  3. After that i copied the tbb4malloc_bi into the Mainfolder, changed the startingparameters to "-malloc=tbb4malloc_bi", so i had two malloc files in this and the server started!
  4. After all i delted the tbbmalloc file out of the main folder, tried to start the server and it crashed.

So what is the correct combination? Do i need 2 files in the mainfolder?

Greetz Lotzo

Edited by Skryp _ LotzoTheUltraBear

Share this post


Link to post
Share on other sites

@Skryp _ LotzoTheUltraBear

Your malloc files need to be in the dll folder. Then do exactly as you were :)

Quick example place tbb4malloc into your dll folder, then use  "-malloc=tbb4malloc"

Edited by DirtySanchez

Share this post


Link to post
Share on other sites
Advertisement

Nope it won't start because you have other issues. Noone can help without more information from you.

Add a spoiler with your rpt.

Add the error messages you get when it won't start.

Share this post


Link to post
Share on other sites

tbbmalloc.dll in Arma3 Directory is used extDB2  (the database extension for Exile)

tbbmalloc4_bi.dll is used by Arma3, by default Arma3 uses this dll.
So unless you are using a custom built .dll for Arma3, don't bother deleting files or overriding the -malloc

 

Share this post


Link to post
Share on other sites

ok i think the problem is something different . i think we have a problem with the Memory and not with the malloc. We have some random crashes " Arma out of memory"....

The first problem was yesterday. here is the part of the rpt log with the Errormessage:

 

15:30:30 Error: PhysX 64: User allocator returned NULL., file ..\..\foundation\src\PsFoundation.cpp, line 240
=======================================================
-------------------------------------------------------
Exception code: C0000005 ACCESS_VIOLATION at 6FABC084
15:30:30 Virtual memory total 4095 MB (4294836224 B)
15:30:30 Virtual memory free 7 MB (7872512 B)
15:30:30 Physical memory free 26828 MB (28131958784 B)
15:30:30 Page file free 30366 MB (31841083392 B)
15:30:30 Process working set 3537 MB (3709071360 B)
15:30:30 Process page file used 3845 MB (4032786432 B)
15:30:30 Longest free VM region: 122880 B
15:30:30 VM busy 4287029248 B (reserved 136175616 B, committed 4150853632 B, mapped 52391936 B), free 7806976 B
15:30:30 Small mapped regions: 15, size 73728 B
graphics:  No
resolution:  160x120x32

 

We are monitoring our server with "marma" and today we had a high peak in the "memory page fault" and the same rpt log like up there (look at pic)  

After the peaks the server crashed and we had to restart manualy.

Some Ideas? 

Bildschirmfoto 2016-01-27 um 22.17.24.png

Edited by Skryp _ LotzoTheUltraBear

Share this post


Link to post
Share on other sites

Arma outof Memory is a bugs with Arma Engine.

Try running the latest perf builds, but there isn't much you can do about it until BIS fixes Arma.
Some people say switching from remoteExec -> Publicvariables with the latest perf builds, helps stop the crashes.

High pagefaults can happen if arma is getting close to high memory, the server is then constantly freeing memory & allocating memory.
If you haven't set your max memory to 3GB,  that will help prevent high memory pagefaults.
ArmaServer really doesn't go much over 2GB in memory usage

 

1 person likes this

Share this post


Link to post
Share on other sites

can u give me the link for the latest perf buildings? 

we don't use the parameter -maxmem ! Should we? 

Our memory is fine the whole time! (see the pic) 

Bildschirmfoto 2016-01-27 um 22.35.17.png

Share this post


Link to post
Share on other sites

Yeah you should use -maxMem=3072
Anything over 3.2GB and you will experience  random crashes

https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm

------------
On your graph arma server is at default max of 2 GB.
When armaserver approaches 90% of max memory it will try to free what memory it can.
So its constantly freeing memory & then allocating more memory, its extra work for the server todo when your server has loads of memory. 
Basically it will effect your server performance, but isn't the reason for your crashes.

2 people like this

Share this post


Link to post
Share on other sites
Advertisement

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

  • Recently Browsing   0 members

    No registered users viewing this page.