updating to 1.12

Should I do it.. everyone ok? I just am weary of the changes. I mean I really am upset that MemAlloced is gone. When I was debugging and looking for a mem leak using CTRL ALT DEL isnt as good and I have to ALT-TAB now? Why make it to where people have to take extra steps to see the mem usage, especially if they're using a full-screen program? CTRL-ALT-DEL isnt as cool as the mem usage commands at all!

I remember I had to re-run a prorgam lik 10x to find a mem leak. Now I have to run the program, then ALT-TAB 10x and that will take longer! (if I run into another mem leak which is probably inevitable considering I'm a newbie!!!!)


I think I'm just going to stay at 1.10 as I noticed 1.12 just gets rid of code (why? remove something? why?) If 1.12 does naything better than just removing code that I wanted to keep then why even update? Please do Correct me if I'm wrong....

On the plus side, you're a lot less likely to run into memoryleaks now 1.12 has its own automated garbage collector and doesn't depend on you using Flushmem() at the right times in the right places anymore.

Yes.

It's been renamed to GCMemAlloced, hardly a drastic change.

Then get Process Explorer from sysinternals.com instead.

You're not going to have any memory leaks anymore, now that you have a real garbage collector. Incidently, to track down memory leaks doesn't take reruns. It takes a program running for a long time (and/or a unit test).

To the best of my knowledge, nothing has been removed (functionality-wise). A good reason for removing or changing something would be because it doesn't work, because it isn't nessecary (ie. it's redundant) or because it's inefficient.

Generally the best way to debug a program is in window mode.


Unless you use Int handles (carelessly) or C strings (instead of $z).

I had a memory leak on an alphablended mouse pointer once, lost a few K every frame = few Mb every second, needless to say it was bad.

Exactly I lost a few k every time and it was easy to find the problem with MemAlloced. Garbage collecter wouldnt fix the problem because it was my coding logic that was the problem.
Now that there is no more MemAlloced, I think I'll stick with 1.10 until I'm sure that I'm not doing anything that'll have me lose a few K every frame.

It hasnt been removed its just renamed to GCMemAlloced


If you use 1.12 you are a lot less likely to get memory leaks.

Dude, I will not lead you wrong (I'm the guy who did your gfx btw :)

UPDATE... your game will most likely be FASTER and more stable... it fixed a LOT of bugs in 1.10.

MemAlloced is still there! Stop being daft... you seriously underestimate how good Mark is at this stuff. He is a seasoned veteran developer.

Just put GC in front of it...

GCMemAlloced()


See? Perfect.


Also, Flushmem made it HARDER to code... now you don't need it with 1.12... what are you waiting for?

Thanks Rob, I'll update my BMax!!! GCMemAlloced() .. Perfect.. Oh and I'm happy to see Flushmem go away :) Just didnt like losing MemAlloced..

Exactly what Bugs did they Fix? I still have problems, in fact the Windows98 problems are worse now!