GitLab

While not a critical memory leak (initialized once) - it still is flagged in all valgrind executions marking large heap of data as being leaked. libpurple_init sets core ops to close and destroy all resources however the actual call purple_core_quit (which then calls the core op chatty_purple_quit) is never executed. Not sure where exactly to place it. Init is called from application->window but neither window nor app has destructor (only stub destructor in app).