[Development] Backporting the "stop unloading plugins" change to 5.6

[Thiago Macieira]

Em sábado, 15 de outubro de 2016, às 15:33:53 PDT, Liang Jian escreveu:
>     But I am still curious about that If we don't unload the plugin, will
> the destructor of the gobal object in it be called? If it is not called,
> what if the gobal object of the plugin hold some memory allocated from heap?

It's easy to test.

In any case, I don't consider leaks those that happen because the memory 
wasn't freed at program exit while holding a pointer to it. In fact, neither 
does valgrind: those are "still reachable" allocations.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center