I have problem with the source code editor in VS Community 2017 Version 15.5.2 and XS Versopm 126.96.36.199.
Error occurs most often after typing "SELF:". After writing a colon, IntelliSense does not appear but freezes Visual Studio.
I need to terminate Visual Studio through the task manager.
Sorry about that. Please give us as more info as possible in order to try to reproduce that problem, or to understand under what circumstances it happens.
Does it happen when typing SELF: inside a specific class, or does it happen in many?
Is it code inside a method, constructor, property or it does not matter?
Does it happen only after a long time writing code, or can it happen also just after you open VS?
Can you zip and send a solution that shows this problem from time to time?
Thanks for the sample, but unfortunately I can't reproduce the problem, seems it's always working here. Does it always happen for you, or only from time to time? What about if you type cName: in the same line, this always works ok? What about "SUPER:"?
I am afraid to say that on my WPF projects and 188.8.131.52 compiler version there is often a definite time 'lag' or delay. I only just noticed it yesterday as I went back to an earlier Project in the same Solution I was working on.
For me it is nothing like as bad as with the previous version, it is workable, but would be annoying to many others I suspect.
I will try and find when it is worse for me - but as you know, it is not easy to pin these things down in a multi tasking environment.
No prob about the bad news, we want people telling us about any issues they have, so we can fix them or provide a solution.
Regarding speed issues, actually we have made some important steps in the last 2 builds to increase the performance in the VS editor, so it should actually be faster than before (it certainly is a lot faster on my machine). But the extra speed does come in the expense of using more memory, sometimes a lot of memory. So in case all the system's memory is used, then the OS can kick in and start swapping memory back and forth to the disk, and if that starts happening, then there will be a big slowdown. The exact same applies to the compiler as well.
Could it be that this is happening when you experience the slowdowns? Maybe you have a lot of programs open at the same time each requiring enough memory and sometimes there's just not more free available? Please check the task manager when the slowdown occurs, how much % free memory does it report? Also what about the CPU usage?
It's without saying that even if this is what turns out to be the problem, we still need to try and improve it, by reducing the memory usage of x#, but in any case it will be a very good first step diagnosing the cause of the slowdown you are experiencing..
I understand what you are saying, and will do all I can to help out.
After posting my last post to you I did some experimenting and had the code editor freeze / lock on me twice for a 5 second period. A bit later, while doing more tests it was 9 seconds. But not easily reproducible
However, this pattern may fit the resource usage of CPU and Memory I suppose.
I will try some further testing tomorrow when I will close down everything else other than VS and X# as well as Help & Manual. I always have that open in order to make the eNotes.
Out of interest to you and others I saw the other day that Edge the Microsoft Browser takes up a BIG chuck of resources, even when it is minimised - but with a few tabs open. May be 10 to 30% CPU at times. And over 4 Gigs RAM ?
Only one problem I can see by hunting down resource hungry stuff etc., is that I do have a very high spec machine - or it was. So really we shouldn't see an issue unless I go crazy with the apps open.
here is my PC spec for your information :-
I fancy closing Edge may have the biggest / best effect.
pmfji, but just in case: it may be no problem with X# at all. For quite some time i hear folks complain, that the OS (possibly Defender) swallows system resources when it sees fit, making for some quite annoying hickups in user experience.
Just a thought...