[Tirant]

I've always wondered, but never asked. In some plugins, scripters who use forwards, arrays, and such, choose to destroy them at plugin_end. I also see some people who do not. I was wondering what would be the effects of not deallocating the memory? Does amxmodx do anything about this on plugin_end?

[Tirant]

I just wanted to add that, what I mean, is like how harmful is it not to destroy these varaibles/etc.

[BAILOPAN]

Plugins and everything they've allocated are freed when the plugin is unloaded. Plugins are unloaded on mapchange. All of this happens regardless of what's in plugin_end.

[ehha]

http://en.wikipedia.org/wiki/Garbage...ter_science%29
I don't know if pawn has it, but from here you can learn something relevant to your question.

[fysiks]

Originally Posted by BAILOPAN Plugins and everything they've allocated are freed when the plugin is unloaded. Plugins are unloaded on mapchange. All of this happens regardless of what's in plugin_end.

Somebody had to submit a patch for a file pointer being left open that didn't get closed. Does this not prove that it doesn't completely clear the memory when the plugin is unloaded?

[xPaw]

Originally Posted by fysiks Somebody had to submit a patch for a file pointer being left open that didn't get closed. Does this not prove that it doesn't completely clear the memory when the plugin is unloaded?

I believe sockets are not closed too.

[joaquimandrade]

Originally Posted by fysiks Somebody had to submit a patch for a file pointer being left open that didn't get closed. Does this not prove that it doesn't completely clear the memory when the plugin is unloaded?

I think he is talking about only of what happens inside plugins and not through module's natives calling. Like, if you call a native that allocates memory, it won't be freed unless the module manages it right. So, the answer to Tirant's question is that it depends on how the module manages it.