Question - IDE [Answered] Does the ds_* generates real memory leak?

[NicoFIDI]

I was wondering if the data structure generates memory leak inside the aplication, or in the ram.
for example if i make

on game start

ds_grid_create(100,100);
game_restart();

will my PC lose all the ram?
or it will be released when the aplication ends?

 

[FrostyCat]

If you don't call the corresponding "destroy" function, data structures remain in memory until a hard exit (i.e. the process disappears off the OS altogether). Your example would constitute a memory leak because game_restart() is not a hard exit.

 

[NicoFIDI]

@FrostyCat
that's a yes?
even in develop time?
so if my application crash on middle of the execution i whould have a memory leak that i cant handle?

 

[GMWolf]

it will be released when the aplication ends?

it will get released when you call ds_*_destroy(), or when the application ends. but at no other time.

 

[NicoFIDI]

ah
ok thanks

 

[psyke]

If you change the room or destroy an object without freeing the data structures or resources, your game will have lots of memory leaks.
GMS2 has a new event called "Clean Up Event", which was made to free resources from the memory. You should put all ds_*_destroy() functions on that event.

 

[NicoFIDI]

Just to avoid more people to get in and explain about memory leaks,
i know how to handle memory leaks,
i alctually had to make my own data structures in C language
my question was about if the game maker memory leaks means:
"real" memory leak (not release ram once the program it's closed).
or "aplication" memory leak (make your aplication take more and more ram but release it when it crush)

 

[GMWolf]

"real" memory leak (not release ram once the program it's closed).

The OS will pretty much always free all the memory allocated by a program once it terminates, regardless of if it's written in C or GM

 

[NicoFIDI]

Nop Fel666.

The ram needs active eletricity to store data.
when you power off or restart your pc the memory it's released without OS intervention.
but it's not the same that the aplication takes a lot of ram (ejample: "MINECRAFT")
or having a aplication take ram away from you until you restart your PC (called: memory leak)

in the programs that run into a virtual machine that's not a problem, because they have garbage collector.
but in C, you can actually take the memory until you power off the ram, if you dont handle it correctly.

 

[zbox]

The OS will pretty much always free all the memory allocated by a program once it terminates, regardless of if it's written in C or GM

Nop Fel666
The ram needs active eletricity to store data.
when you power off or restart your pc the memory it's released without OS intervention.
but it's not the same that the aplication takes a lot of ram (ejample: "MINECRAFT")
or having a aplication take ram away from you until you restart your PC (called: memory leak)

School'd Fel666, who knew RAM needs electricity to work eh ?

 

[NicoFIDI]

School'd Fel666, who knew RAM needs electricity to work eh ?

also ROM doesnt need it to keep data

 

[zbox]

also ROM doesnt need it to keep data

I feel bad now - I was being sarcastic

 

[GMWolf]

Nop Fel666.

The ram needs active eletricity to store data.
when you power off or restart your pc the memory it's released without OS intervention.
but it's not the same that the aplication takes a lot of ram (ejample: "MINECRAFT")
or having a aplication take ram away from you until you restart your PC (called: memory leak)

in the programs that run into a virtual machine that's not a problem, because they have garbage collector.
but in C, you can actually take the memory until you power off the ram, if you dont handle it correctly.

Even when writing in C, the OS has got your back.
When allocating memory, you are not actually interfacing directly with the hardware. You are asking the OS to allocate memory.
The oS interfaces with the hardware and allocated memory. What it returns to the software is a virtual address space.
This means that programs are isolated from each other (a pointer in one program can have the same value as a pointer in another program without them being the same physical adress).

The os keeps track of what memory is allocated to what process, and when the process ends, it marks the memory as free, ready to be reused by another process (it may even clear the memory for security, but not necessarily).

You can easily test this yourself:
Create a C program that calls calloc continually. When it reaches 2 GB of mem usage or so, kill it, and obsrve your ram usage.

 

[NicoFIDI]

I didnt know that OS update D:
it's nice to know that now they take care of it
welp, with that knowledge the post didnt actually make any sense.
thanks @Fel666