Try to disable symbols browser.
I think now the symbols browser is *NOT* thread safe.
Maybe this is the final reason.
I'll try, but actually I doubt this will be the reason, too. I am using one parser per WS only, so only one parser feeds the symbol browser. This should not fail and progressing is basically serialised.
I believe it's related to the different set of macros. What happens e.g. if the same wx file is parsed with different
#defines? Imagine you have a project (target) using ANSI and one using Unicode. What will be added to the (internal/symbol) tree?
Similar is the case in the sample I provided: static and dynamic linking requires different
#defines. All other projects I had in this WS (before stripping it down to what it is now) caused no problems. Just these two.