Author Topic: TLSFMem O(1) Memory Allocator (Read 8775 times)

JosephC · « **on:** October 15, 2007, 04:08:22 AM »

Hooray!!!

But is it any better than MemOptimizer?
Or Poolmem?

JosephC · « **Reply #1 on:** October 15, 2007, 09:50:32 AM »

@Piru

I thought that PoolMem patched AllocMem() to allocate memory in a less fragulated way?

JosephC · « **Reply #2 on:** October 15, 2007, 09:54:12 AM »

Is there any way to rewrite MuForce, MuGuardianAngel, MungWall, etc. to work with the new ChrisHodges(tm) TLSF patch?

JosephC · « **Reply #3 on:** October 16, 2007, 11:21:13 AM »

I want this patch to become the standard.
But I don't see how that will happen when it can't be run with debugging software such as MuGuardianAngel.

What can we do to make MuGuardianAngel cooperate with TSLFMem?

Please someone must have the answer!

JosephC · « **Reply #4 on:** October 21, 2007, 03:59:19 PM »

A1: Probably Yes. I had the same problem on my system and both PoolMem or TLSFmem solve it for me.

A2: Should be 100% safe.

JosephC · « **Reply #5 on:** October 26, 2007, 06:19:44 PM »

@ChrisH

Check your Startup-Sequence for anything that might be patching your memory allocation routines. MCP? PoolMem? MemSniff? MungWall? Ixemul?

Author Topic: TLSFMem O(1) Memory Allocator (Read 8775 times)

JosephC

Re: TLSFMem O(1) Memory Allocator

JosephC

Re: TLSFMem O(1) Memory Allocator

JosephC

Re: TLSFMem O(1) Memory Allocator

JosephC

Re: TLSFMem O(1) Memory Allocator

JosephC

Re: TLSFMem O(1) Memory Allocator

JosephC

Re: TLSFMem O(1) Memory Allocator