Comment #0 by michal.minich — 2013-09-25T05:57:37Z
It happens only when Alexander Bothe's D parsing engine is turned on. The process uses CPU at about 40-80% or occasionally 95%, constantly, on 2 core machine. It start up when one character is source code is changed and never stops. It happens even when there is only one trivial D file in project. I guess it might be because it tries to follow VisualD import settings (vibed in this case). It does not happen for all solutions. I can investigate more details if needed.
This makes it very limited use for me as it drains laptop battery.
Comment #1 by r.sagitario — 2013-09-25T23:53:08Z
Last time I noticed this it was an infinite loop in the parser (the fix should be in 37rc3). I've just tried browsing the vibe.d project, but that did not cause any issues.
It would be good if you could isolate a file or code snippet that reproduces this.
Comment #3 by michal.minich — 2013-10-06T01:20:07Z
(In reply to comment #2)
> There is a new rc with a number of fixes in the D parser engine:
> http://www.dsource.org/projects/visuald/browser/downloads/VisualD-v0.3.37rc4.exe
> Please try that.
Thank you.
That fixes it.
After initial few seconds of high CPU usage, it goes down. Then it keeps at 0-5% when idling or changing the code.
Comment #4 by r.sagitario — 2013-10-06T03:14:52Z
(In reply to comment #3)
> After initial few seconds of high CPU usage, it goes down. Then it keeps at
> 0-5% when idling or changing the code.
The initial seconds is when it parses the files found through the import paths and is to be expected. During that time completion and tool tips don't work yet.