If by crash handler dialog you mean this dialog on the
screenshot, then yes. Otherwise no. If yes - you have it's content in my previous post (it's the same every time).
It might be helpful - it seems that C::B is stuck somewhere waiting for something because windows won't realize that it stopped responding until I demand it to do something (for example switch focus to C::B window, or just click somewhere inside the window). It then goes white and... does nothing. The dialog from the screen shows once I press close button and wait for a while.
Yes I've tried waiting for an hour letting C::B do it's stuff, but the cpu usage was at 0%, and ram amount didn't change so I decided to terminate the process.
Btw, if you want me to collect some more data about this bug, tell me what to do because I have no idea on how to provide more info.
Oh, and on the screen C::B hang after opening typedefs.h (I opened my indexer.hpp file, then closed it, opened typedefs.h and program freezed).
And sorry for giving you a link to the screenshot, but it was too big (196kB) to send it as attachment.