506th IR Realism Unit
Open Forum => Public Discussion => Topic started by: PV2 Patch on October 05, 2015, 06:38:28 PM
-
Arma 3 when joining 506th servers provides this message: The instruction at 0x4f656b61 referenced memory at 0x4f656b61. The memory could not be written.
It then closes Arma. Parameters are, CPU count: 4, MaxMem: 32768, MaxVRam: 6192, NoSplash: Enabled, Skip Intro: Enabled.
Why is it giving me the error?
-
Add the line '-malloc=system' to your startup parameters OR, if you are using the Arma 3 launcher, in Parameters > Advanced > Advanced check 'Malloc' and type 'system'
http://www.506thir.net/forums/index.php?topic=7184.0
-
Would also try deleting your DLL's. That seems to have helped a lot of people with varied problems. Speak to PFC. E. Wolfe on TS if you see him on, he's very good with the mods.
-
Add the line '-malloc=system' to your startup parameters OR, if you are using the Arma 3 launcher, in Parameters > Advanced > Advanced check 'Malloc' and type 'system'
http://www.506thir.net/forums/index.php?topic=7184.0
^^^ Do not do this.. However Deleteing your Dll's Will solve the issue
-
ROLF - that's hilarious: I deleted my DLL's to fix mine, and I had been told not to do that but to change my "malloc" setting. Now you say the opposite lol....I did both, and I'm fine now, so whatever works I guess.
-
Add the line '-malloc=system' to your startup parameters OR, if you are using the Arma 3 launcher, in Parameters > Advanced > Advanced check 'Malloc' and type 'system'
http://www.506thir.net/forums/index.php?topic=7184.0
^^^ Do not do this.. However Deleteing your Dll's Will solve the issue
Both thing accomplish that same thing to be honest. If you notice the DLLs in the DLL folder are all different mallocs. Setting the malloc to system causes ArmA to use the memory allocater that comes with your OS instead of the custom ones created by Bohemia. Deleting the DLLs cause ArmA to use the memory allocater that came with your OS as well since it can't find any in the DLL folder.
I've successfully removed the error by setting malloc to system. Either solution should technically work. Though if you set your malloc to system you don't ever have to worry when ArmA re downloads the DLLs during an update.