The process "COM Server for DParser"; after I've been running Visual Studio for a while, this service grows to use a lot of resources.
The creeping memory is one thing, but I also experience creeping passive CPU usage.
After a while, I see constant CPU usage sitting around 20% of my machine (which is a very fast machine) while all other processes are idle, and my CPU fan is running hard and noisy.
When I terminate Visual Studio, the process remains active and there is no change in resource usage.
I find I have to manually terminate this process from time to time and restart Visual Studio to stop it leaking.
Why would the idle CPU usage be leaking even if there's no client app running and making use of the service?
Comment #1 by rswhite4 — 2013-11-20T06:14:08Z
Please post it here: https://github.com/aBothe/D_Parser/issues
Alex does not read regularly here. Also it would be helpful if you give him more information about your project, and if you have enabled specific settings, e.g. the mixin resolution.
Comment #2 by turkeyman — 2013-11-20T07:23:56Z
(In reply to comment #1)
> Please post it here: https://github.com/aBothe/D_Parser/issues
> Alex does not read regularly here. Also it would be helpful if you give him
> more information about your project, and if you have enabled specific settings,
> e.g. the mixin resolution.
I didn't realise this process was strictly Alexander's engine. I thought it was VisualD that factored all if it's semantic analysis stuff into a separate process for garbage collection reasons?
Is there an option for mixin resolution? I never saw that option anywhere... where should I find it?
As far as I can tell, I'm running entirely default settings.
Comment #3 by rswhite4 — 2013-11-20T08:18:08Z
No, DParser is the work of Alex. ;)
For further questions ask him or take a look on his website. :)
Comment #4 by r.sagitario — 2013-11-20T14:46:25Z
The CPU "idle" usage probably means it is running full speed on a single core. I guess this happens because the engine is locked in some infinite loop.
Yes, Alexander's engine is now the default, as it is both faster and more complete than the original engine in Visual D. You can switch back to the other engine by disabling the Alexander's on the "Intellisense" page.
Both UFCS and mixin-analysis are enabled in the engine.
A lot of fixes have been made in D_Parser (including a timeout on completion request), so this should no longer be an issue.
Please try it in Visual D 0.3.38
Comment #7 by r.sagitario — 2014-08-02T13:14:26Z
I guess we can close this as being fixed since 0.3.38