Closed madskristensen closed 1 year ago
Looks more like concurrency issue. Default dictionary capacity is 3. I've added fourth pair ('<' and '>') and then the dictionary can be in corrupted state and can end in infinite loop.
The SaveToCache()
should be called once per ParseAsync()
and set up to 4 entries.
I'll have a look.
Our Visual Studio telemetry that monitors high-CPU also captured this problem, thanks for the fix @lordfanger!
I'm sorry I read the callstack wrong. The problem was in async await method (RainbowBraces!RainbowBraces.RainbowTagger+d__25.MoveNext()
). And somehow I overlooked it previously. It should be fixed now in #66.
We have a callstack showing some threads going crazy in the extension:
It looks like we are saving to cache too frequently.
@lordfanger what do you think?