<![CDATA[QPluginLoader memory location]]>HI,

QpluginLoader loads library returns instance of library.
Return instance is created at stack memory or heap memmory, how to check memory allocation place?

Thank you in advance.

]]>https://forum.qt.io/topic/77532/qpluginloader-memory-locationRSS for NodeThu, 11 Jun 2026 01:01:54 GMTFri, 24 Mar 2017 04:33:14 GMT60<![CDATA[Reply to QPluginLoader memory location on Mon, 27 Mar 2017 03:39:45 GMT]]>@jsulm thank you.
As i made test to check the memory allocation using threads, it confirmed that loaded plugin is not on stack , mostly on heap.

]]>https://forum.qt.io/post/384307https://forum.qt.io/post/384307Mon, 27 Mar 2017 03:39:45 GMT<![CDATA[Reply to QPluginLoader memory location on Fri, 24 Mar 2017 07:44:07 GMT]]>Hi,
The Instance , returned by this function, is not deleted when the QPluginLoader is destroyed. If you want to ensure that the instance is deleted, you should call unload() as soon you don't need to access the Instance anymore. When the library is finally unloaded, the Instance will automatically be deleted.

]]>https://forum.qt.io/post/383925https://forum.qt.io/post/383925Fri, 24 Mar 2017 07:44:07 GMT<![CDATA[Reply to QPluginLoader memory location on Fri, 24 Mar 2017 05:24:48 GMT]]>@yuvaram It for sure does not allocate the memory on the stack. Stack is only used for function calls: function call frames including the address to jump back after function execution, function parameters and local variables in the function.
QPluginLoader actually does what dlopen() system call does on UNIX systems, so you can check there how it loads the library (a plug-in is just a shared library).

]]>https://forum.qt.io/post/383902https://forum.qt.io/post/383902Fri, 24 Mar 2017 05:24:48 GMT