Skip to content


Delete authentication manager after destruction of the providers
Browse files Browse the repository at this point in the history
The providers may still have threads running that use the authentication manager and their finished signal might trigger logic in the authentication manager.
  • Loading branch information
m-kuhn committed Feb 26, 2019
1 parent 1e49bb1 commit 854a904
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/core/qgsapplication.cpp
Expand Up @@ -1177,8 +1177,6 @@ QgsAuthManager *QgsApplication::authManager()

void QgsApplication::exitQgis()
delete QgsApplication::authManager();

//Ensure that all remaining deleteLater QObjects are actually deleted before we exit.
//This isn't strictly necessary (since we're exiting anyway) but doing so prevents a lot of
//LeakSanitiser noise which hides real issues
Expand All @@ -1191,6 +1189,8 @@ void QgsApplication::exitQgis()

delete QgsProviderRegistry::instance();

delete QgsApplication::authManager();

// invalidate coordinate cache while the PROJ context held by the thread-locale
// QgsProjContextStore object is still alive. Otherwise if this later object
// is destroyed before the static variables of the cache, we might use freed memory.
Expand Down

0 comments on commit 854a904

Please sign in to comment.