Hi,
I am experiencing a very high and persisting consumption of CPU and memory:
I have just opened our workspace and the load now keeps being like that for at least 10min. Doing nothing else, ALs own opening crescendo has long died down.
Using Version 3.0.35
Other developers in our organization have reported similar, also from two weeks ago. There MAY or may not have been the windows search indexer been involved, In one case fixing a rampant win search index job also seemed to have fixed this extension. But do not treat this as given, may well be coincidence and anyway there is no good way to repro.
EDIT:
Closed and restarted VS Code, with one codeunit opened -> memory usage just about the same but no more rampant CPU consumption. Okay.
Then closed and restarted VS Code with the workspace active but no al file opened -> CPU consumption is just as high initially but quickly fell to zero. Also Okay,
Maybe just a transient thing... anybody else experienced this?
Hi, I am experiencing a very high and persisting consumption of CPU and memory:
I have just opened our workspace and the load now keeps being like that for at least 10min. Doing nothing else, ALs own opening crescendo has long died down.
Using Version 3.0.35
Other developers in our organization have reported similar, also from two weeks ago. There MAY or may not have been the windows search indexer been involved, In one case fixing a rampant win search index job also seemed to have fixed this extension. But do not treat this as given, may well be coincidence and anyway there is no good way to repro.
EDIT:
Closed and restarted VS Code, with one codeunit opened -> memory usage just about the same but no more rampant CPU consumption. Okay.
Then closed and restarted VS Code with the workspace active but no al file opened -> CPU consumption is just as high initially but quickly fell to zero. Also Okay,
Maybe just a transient thing... anybody else experienced this?