tonyw wrote:BTW, why do you use obsolete system calls like AllocMem() and FreeMem() ?
What does that have to do with reputation ? If there's a bug, and someone can deliver a test case that shows it, then I'll gladly acknowledge that I made a mistake and can correct it.
It's not that simple. I tried it, and it didn't lock up at first... I repeated the allocation->deallocation cycle several times, until it finally locked up. It's not as simple as re-allocating something that has been paged out before. It might also be a race condition. I will have to find out what exactly is happening to be sure.
Question still stands, did it happen on anything prior to Update 4 ?
xenic wrote:Maybe because there are no warnings when compiling those functions.
Deniil wrote:Yes, update 3 had the same problem, but not update 2.
That is very useful information for the developers.
ssolie wrote:xenic wrote:Maybe because there are no warnings when compiling those functions.
You will in the next SDK...
We will also try to explain why they should be avoided in the new wiki which is on it's way.
Users browsing this forum: No registered users and 1 guest