Ah yeah i see what your saying,
Well the other reason i wanted to do _NO_DEBUG_HEAP
Because in release the application messes up crashes more often in debug this is not the case.
As FakeTruth explained me before its because in debug bigger space is added between everything in memory.
So less chance of it overwriting something if it go's outbounds. i thought _NO_DEBUG_HEAP would remove that big space.
So i might actually get the same problem in debug and it would make the server crash so i can find where it screws up.
As atm i simply have no clue..
And i didn't write the code so i might have to check some stuff :p.
but here's a bit of info its a server app.
Multi threaded doesnt seem to lockup anywhere.
all threads have a while loop with a small sleep in it.
in those while loops it mostly loops tru all connections a few times.
like one to see if new packets are arrived etc.
But i need to find where the problem lies of what is overwriting memory, out of bounds.. as it doesn't trow a error or anything.
If i can fix this i can probably run it normally in release without many problems.
Edit:
Btw running it without a debugger attached doesnt seem to make any differents..
Unless that only affects cpu load and not memory. as atm as i run it local i can only see a differents in memory for 1 player for 74mb release mode, 400+mb debug mode.
that doesnt change when running it without debugger attached. so i asumed it didnt work and the cpu wouldnt drop as well.
Well the other reason i wanted to do _NO_DEBUG_HEAP
Because in release the application messes up crashes more often in debug this is not the case.
As FakeTruth explained me before its because in debug bigger space is added between everything in memory.
So less chance of it overwriting something if it go's outbounds. i thought _NO_DEBUG_HEAP would remove that big space.
So i might actually get the same problem in debug and it would make the server crash so i can find where it screws up.
As atm i simply have no clue..
And i didn't write the code so i might have to check some stuff :p.
but here's a bit of info its a server app.
Multi threaded doesnt seem to lockup anywhere.
all threads have a while loop with a small sleep in it.
in those while loops it mostly loops tru all connections a few times.
like one to see if new packets are arrived etc.
But i need to find where the problem lies of what is overwriting memory, out of bounds.. as it doesn't trow a error or anything.
If i can fix this i can probably run it normally in release without many problems.
Edit:
Btw running it without a debugger attached doesnt seem to make any differents..
Unless that only affects cpu load and not memory. as atm as i run it local i can only see a differents in memory for 1 player for 74mb release mode, 400+mb debug mode.
that doesnt change when running it without debugger attached. so i asumed it didnt work and the cpu wouldnt drop as well.