Unhandled exception While Allocating Memory

[Thothie]

Eh, still says AMX2006... If ya get it working with AMXmodX, I'll be impressed, as one of their former team members failed in the effort. But still, it would create the issue that it couldn't capture our map transition attempts.

 

[pimpsta]

alright, I will work on amx2007...

 

[Humming Bird]

Eh, still says AMX2006... If ya get it working with AMXmodX, I'll be impressed, as one of their former team members failed in the effort. But still, it would create the issue that it couldn't capture our map transition attempts.

I've tried it before. I even asked them to convert the edits you did to AMX2006 admin.sma

They said: You made too many edits, cannot be converted.

Then I tried converting it on my own using WinMerge.
Wayyy too hard, their admin.sma code is different than AMX2006's, so I had no luck.

 

[pimpsta]

I was able to get amx2007 working but it kept constantly crashing the players that keep joining the server. They would tell me reliable channel overflow.

 

[Thothie]

Eh... SFAIK - There is no AMX2007. The AMX project died with AMX2006. There is only AMXmodX.

I've tried it before. I even asked them to convert the edits you did to AMX2006 admin.sma

They said: You made too many edits, cannot be converted.

Then I tried converting it on my own using WinMerge.
Wayyy too hard, their admin.sma code is different than AMX2006's, so I had no luck.

There are no edits to admin.sma, save for the slap delay. If someone said they couldn't convert that, they are on the crack.

None of our AMX plugins generate new edicts.

AMXmodX can only do what our plugins do through FakeMeta, as they removed the commands we need several versions ago, but AMXmodX is not compatible with Master Sword, sfaik, so it doesn't much matter. ModX hates lots of mods as, unlike the original team, the ModX team only cares about mods they actually play.

 

[pimpsta]

don't worry... I will make it work!

 

[pimpsta]

This will fix the issue for this subject...

1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: PoolUsageMaximum
Data type: REG_DWORD
Radix: Decimal
Value data: 60
Setting the value at 60 informs the Memory Manager to start the trimming process at 60 percent of PagedPoolMax rather than the default setting of 80 percent. If a threshold of 60 percent is not enough to handle spikes in activity, reduce this setting to 50 percent or 40 percent.
Value name: PagedPoolSize
Data type: REG_DWORD
Radix: Hex
Value data: 0xFFFFFFFF
Setting PagedPoolSize to 0xFFFFFFFF allocates the maximum paged pool in lieu of other resources to the computer.
4. Quit Registry Editor.
5. Restart the server for the changes to take effect.

 

[Thothie]

Umm... Where, pray tell, did you come accross this suggestion?

 

[pimpsta]

I have done this and still working on it. If you know your memory well enough and find out what the right 0000000 number you need to add in your regedit file then use that number. It helped reduce mine a lot but still playing with the numbers until I don't get the errors. Before I did the configure I was getting like 40 to 200 error pop up. now I am getting 1 to 10 errors on server. Which it is better than it was before.

 

[Thothie]

Meh, I still think it's coincidence (right up there with "amx_map fixed it"). This phenomenon varies extremely - I can go for days and not see at all, then get like 10 times in the same hour. It varies with the combination of characters on the server.

 

[Blasto121]

MS:C doesn't manage memory very well thats all there is to it, pimpsta's suggestion is an odd one and I can see how it helps. However in the end its something that will have to be fixed in the hard code.

For those that don't understand what pimpsta's suggestion does:

Basically it takes the page/virtual memory your system has and cleans it out.

So if the number by default is 80 that means when 80 percent of your page files are full it starts looking at the old files in it and removing them.

This is to keep it clean, so by making the number smaller it starts doing that task sooner. So hopefully it will clean out the bad MS:C memory reference before the program attempts to do it itself.

Personally I just stick with no paging files

However that will slow down your system, because windows requires its page files to run fast, which is odd because normal ram is just oh so much faster than a HDD.

At least it won't slow down programs!

 

[Thothie]

Actually, I remember we tried running a server without paging files to fix this, and well, it didn't. It, however, didn't slow down the server too much (I suppose it won't, so long as you have sufficient memory and aren't using it for other things).

 

[Blasto121]

it helps a little compared to paging files because ram is faster, I know it doesn't solve the issue, but it does help with it. I ran without paging files and barely saw the error.

In the end try as you might this error is here to stay.

 

[Jelly]

Necropost to say: I just had the error, but I didn't crash! Game kept running!

 

[Mikkel]

Happens to me all the time
I have to click ok ok ok ok ok ok

 

[Thothie]

Better to close it or let it crash proper, otherwise it risks corrupting clients characters.

 

[Dridmar]

Better to close it or let it crash proper, otherwise it risks corrupting clients characters.

Whoops, now you say that. It has happened a couple time to me and I just keep clicking ok. :?

 

[Mikkel]

Thinking the same

 

[pimpsta]

doesn't happen to me much if I do this settings. When it does, I let it crash proper instead of hitting ok, ok, ok, ok, ok

 

[Teh]

I get this when I try to join a server, or make my own. I was just afraid to bump my thread.

 

[pimpsta]

yes I have been getting this lately with my server.