| commit | 4823ae39c9fab9acca0e294e1ce7ca8d4bb77e13 | |
| author | dyen <dyen@chromium.org> | |
| Tue, 28 Jul 2015 21:34:37 +0000 (28 14:34 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Tue, 28 Jul 2015 21:35:14 +0000 (28 21:35 +0000) | ||
| tree | 5ff6891fc4fd2041d783ab7e7a6a48d7368c7e22 | treesnapshot (tar.gz zip) |
| parent | 48d359b13c0f60e444280afc03df8dfeb8ebe41d | commitdiff |
Make sure active queries map is cleared upon query manager destroy.
When the active queries map was not cleared, it could possibly
cause an assert in QueryManager::~QueryManager() when it validates
that all queries have been deleted. This is because the active
queries map holds a reference to the query.
BUG=509896
Review URL: https://codereview.chromium.org/1261653003
Cr-Commit-Position: refs/heads/master@{#340770}
When the active queries map was not cleared, it could possibly
cause an assert in QueryManager::~QueryManager() when it validates
that all queries have been deleted. This is because the active
queries map holds a reference to the query.
BUG=509896
Review URL: https://codereview.chromium.org/1261653003
Cr-Commit-Position: refs/heads/master@{#340770}
| gpu/command_buffer/service/query_manager.cc | diffblobblamehistory |