[215] getting crazy here...

Hi,

This is a rant... er... call for help.

Build 215 has been pretty much usable all the past week, but today it looks
like it wants to make me shoot myself.

I've been getting the 3 most annoying bugs (at least for me) in quick
succession, non-stop since this morning (nearly 12pm here) :
- identifier shown on a black background (ok, VS bug I know, that's just the
least annoying of the three). Only solution when it happens -> restarting
VS.
- 100% CPU used by the analysis engine whenever a file is open. I have no
clue as to what triggers it, but it's by far the first on my "please fix
this quickly" list. Only solution when it happens -> restarting VS.
- loss of keyboard shortcuts. More precisely RS resets the shortcut keys to
its default, removing the other shortcuts I made for some RS actions and
taking over shortcuts I use for non-RS functions. Needless to say, this is
very annoying. Only solution when it happens -> changing (yet again) all
shortcuts... That's second on my "please fix this quickly" list.

Small example of the latest sequence, just before I wrote this post :
- I'm working on a file, classic class, nothing exotic
- I make a rename refactoring on a local variable. I write the new name, hit
space/enter/whatever and the autocompletion replaces the new name with
whatever was last in the suggestions (a completely irrelevant name).
- I undo. RS loses its mind, throws an exception, screws up its highlight.
- while closing/reopening the file to try to refresh the highlight (without
much success), the identifier coloring bug shows its face.
- I close/restart VS (feels like I spent most of the morning doing this)
- I reopen the file, highlighting fixed, I'm resuming work. Or so I thought.
- I hit Alt-1 (a shortcut I use for QuickFix, easier to use than Alt-Enter),
it doesn't work. I check in the options and yes, RS has reset all its
shortcuts.
- I'd love to change all shortcuts back, but the 100% CPU bug has also
appeared, so I first need to close/restart VS again.
- I come here and write this post before I'm unable to write anything with
the smallest amount of self-control.

(in this case there was an exception from RS, but it's not needed for those
bugs to appear, unfortunately...)


I'd really love to hear from someone having the same troubles (at least I'd
feel less lonely), but I'd love even more hearing that the two last bugs
(100% CPU use and resetting of shortcuts) are known and will be fixed soon.

As said in the subject, I'm getting crazy here...


Lionel


4 comments
Comment actions Permalink

Hello Lionel,

- identifier shown on a black background (ok, VS bug I know, that's
just the
least annoying of the three). Only solution when it happens ->
restarting
VS.

It's not the only one. You can also swith the identifier highlighting off.

- 100% CPU used by the analysis engine whenever a file is open. I have
no
clue as to what triggers it, but it's by far the first on my "please
fix
this quickly" list. Only solution when it happens -> restarting VS.

I guess JetBrainers will be happy if you attach a debugger and get a stacktrace
of such hung VS for them.

- loss of keyboard shortcuts. More precisely RS resets the shortcut
keys to
its default, removing the other shortcuts I made for some RS actions
and
taking over shortcuts I use for non-RS functions. Needless to say,
this is
very annoying. Only solution when it happens -> changing (yet again)
all
shortcuts...

Well.. why don't you backup your keyboard settings?

Best regards,
Maxim



0
Comment actions Permalink


"Maxim Babenko" <mab@shade.msu.ru> wrote in message
news:11564632742409739531250@news.intellij.net...

- identifier shown on a black background (ok, VS bug I know, that's just

the

least annoying of the three). Only solution when it happens ->

restarting

VS.

It's not the only one. You can also swith the identifier highlighting off.


Yup, but I've gotten quite used to it :) And since it's (usually) not that
frequent, I'd rather not disable it.

My main problem, by far, is the next one:

- 100% CPU used by the analysis engine whenever a file is open. I have

no

clue as to what triggers it, but it's by far the first on my "please fix
this quickly" list. Only solution when it happens -> restarting VS.

I guess JetBrainers will be happy if you attach a debugger and get a

stacktrace

of such hung VS for them.


That's the problem with this bug. VS is not hung, there are no exception,
it's simply abysmally slow. Technically still usable, if you consider that
waiting a second between each keystroke is usable.

If there's way to log something in this case, I'm all for it.

- loss of keyboard shortcuts. More precisely RS resets the shortcut keys

to

its default, removing the other shortcuts I made for some RS actions and
taking over shortcuts I use for non-RS functions. Needless to say, this

is

very annoying. Only solution when it happens -> changing (yet again)

all

shortcuts...

Well.. why don't you backup your keyboard settings?


That's what I'm ending up doing, but it would be much better if it didn't
happen :)
This one has been a little surprise today. I don't remember encountering
this bug before, even though absolutely nothing changed in my configuration
since last week.

Also, RS has been much friendlier this afternoon, don't ask me why...


Basically, the main point behind this post (besides ranting, now that I've
been able to do some work without fighting RS every few minutes) was to know
if someone else has encountered this 100% CPU usage bug.
I haven't found references to it in the tracker, and since it's not really
traceable (random, not an exception, not a freeze, not a crash, ...), it may
be useful to see if others have had more luck in pinpointing the cause.


Lionel


0
Comment actions Permalink

Hello Lionel,

That's the problem with this bug. VS is not hung, there are no
exception, it's simply abysmally slow. Technically still usable, if
you consider that waiting a second between each keystroke is usable.

If there's way to log something in this case, I'm all for it.

You can attach a debugger to the hung instance of devenv and capture the
stacktrace once you come across this problem again.

Best regards,
Maxim



0
Comment actions Permalink

"Maxim Babenko" <mab@shade.msu.ru> wrote in message
news:11567632742440077031250@news.intellij.net...

That's the problem with this bug. VS is not hung, there are no
exception, it's simply abysmally slow. Technically still usable, if
you consider that waiting a second between each keystroke is usable.

>

If there's way to log something in this case, I'm all for it.

You can attach a debugger to the hung instance of devenv and capture the
stacktrace once you come across this problem again.


I just posted an entry in the tracker about this. I just noticed this
(currently) happens everytime I go in Tools/Options. Another mystery. I went
there many times since 215 is installed, and if this happened each time, I
probably would have remembered. But then, I've been known to overlook pretty
obvious things :)

I added the stack trace (I'll have to remember to do this with the next bug
of this kind :)


Regards,

Lionel


0

Please sign in to leave a comment.