vim/YouCompleteMe
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Destroying clang data last, after threads done

Browse Source 
Otherwise this will cause issues if the clang threads are still trying to
access the clang data.
This commit is contained in:
Strahinja Val Markovic 2013-02-16 12:24:00 -08:00
parent f01a3480f5
commit 90dc16bb99
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
cpp/ycm/ClangCompleter/ClangCompleter.cpp
View File

@ -88,11 +88,6 @@ ClangCompleter::ClangCompleter()
ClangCompleter::~ClangCompleter() { ClangCompleter::~ClangCompleter() {
// We need to clear this before calling clang_disposeIndex because the
// translation units need to be destroyed before the index is destroyed.
filename_to_translation_unit_.clear();
clang_disposeIndex( clang_index_ );
{ {
unique_lock< shared_mutex > lock( time_to_die_mutex_ ); unique_lock< shared_mutex > lock( time_to_die_mutex_ );
time_to_die_ = true; time_to_die_ = true;
@ -105,6 +100,11 @@ ClangCompleter::~ClangCompleter() {
clang_thread_->interrupt(); clang_thread_->interrupt();
clang_thread_->join(); clang_thread_->join();
} }
// We need to clear this before calling clang_disposeIndex because the
// translation units need to be destroyed before the index is destroyed.
filename_to_translation_unit_.clear();
clang_disposeIndex( clang_index_ );
} }