What the hell is a heap dump? Mine's like 1 gig

lmao idk what it is but mine is 3.61 MB

xDDD 1 gig!?

actually no
I was wrong
I was a bit off
Its 9.8 gig!

At first i assumed that 10,280, 420... was 1gb but the ... was more of a ....................... it turns out

10,280,420 is actully 10.28042 gig. Dont be dopy

make a copy and then and the old one delte the text from the top like your clearing your debug and see what happenes

dude, just delete it. it only exists to show the map compiling process.
delete it and it will make a fresh one on next map compilation.

mine was like 12 gb before i deleted it.

Headnoob u are an idiot.

It said 10, 280, 420..... but when i selected it, it was 9.8 so stuff u. Just.... go away

It could be both, he's not wrong completely... He's thinking in decimal/base ten, while computers think of memory in as 8Bits=1Byte, and for the rest in binary. Aka 1KiB=1024Bytes. So 10,280,420 KB would equal 10.280GB, but 9.8GiB, which is what the computer displays to you.

I think I got that right. It's a weird concept, and it's why a few years back people were complaining about getting 1TB HDDs that only had ~937GB(actually GiB) of usable space.

1Kilobyte technically is 1000 bytes, but it depends on what standard you use. The lower hard drive space is caused by formatting. And you're getting your ratios wrong for bits versus bytes. If 1 byte = 8 bits, 10.28 GB cannot equal 9.8 Gb.

Edited by Co1t3r on Nov 11, 2010 at 11:33 PM

I know 10.2GB =/= 9.8Gb. GiB is the binary prefix, not the decimal GB. So it's gibibyte and gigabyte respectively.

en.wikipedia.org/wiki/Binary_prefix Is what I was talking about. I may still be wrong, but that's at least what I meant.

Forgot about formatting of drives too, however, that's not the complete reason.

Just did the math. 10280420KB = 9.8GiB (which the computer displays simply as 9.8GB). Divide 10280420 by 1024 twice. You'll get 9.8.
Edited by Caboose117 on Nov 11, 2010 at 11:43 PM

all I have to say is:

Holy....crap

You shouldn;t let your heap dump exceed 50mb.
Delete it every so often. I delete it after every 3 map compilations.

whats so bad about letting it exceed 50 mb?

It is unnecessary. I would rather not have a big ass text file, because that's retarded.
Just make deleting debug.txt and heap dump part of you map compilation process.

so the debug will come back like the heap dump does when an error occurs?

Yes. Debug is recreated if there is an error, and heap dump is made every time you compile a map.

cool. That should free up some memory on the pc

But you haven't restarted your computer?!
Oh you mean DISK SPACE.

Proper terminology plz. XD

They're interchangeable. Unless you're talking about hardware, nobody cares, everyone gets what he meant.

My terminology was fine i thought. Although, Sapien is the most compliecated thing I can do on computers