[2150] Throw New no intellisense and causes CPU thrashing

When I start typing

Throw New Arg

Instead of being presented with intellisense to select ArgumentException R# causes full core thrashing for 1 core (perfect 50% cpu usage), ram climbs 50MB~, no answers are returned. When I finished self typing it eventually R# would stop thrashing, I guess from bailing on the attempt to auto complete.

7 comments

Just a word to say that I can reproduce this too.

This seems to be a new R# 6 feature that was missing from previous versions: complete a new statement with all possible derived types constructors. However, this great feature slows everything down when trying to instantiate an exception (as in Chris' post) or a delegate.

--
Julien

0

Yes, I've noticed this too, though I seem to be blessed with a machine that doesn't go away and thrash for ages. It just feels sluggish when completing a throw new xxx.

0

Hello Chris,

There's a corresponding bug-report in our tracker: http://youtrack.jetbrains.net/issue/RSRP-259949
and you're welcome to vote for it. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

When I start typing

Throw New Arg

Instead of being presented with intellisense to select
ArgumentException R# causes full core thrashing for 1 core (perfect
50% cpu usage), ram climbs 50MB~, no answers are returned. When I
finished self typing it eventually R# would stop thrashing, I guess
from bailing on the attempt to auto complete.

---
Original message URL:
http://devnet.jetbrains.net/message/5302911#5302911



0

Hi Andrew,

you should probably change the status from "fixed" to something else..

Henning

"Andrew Serebryansky"  wrote in message
news:c8a898dd10e568cddeaf2664b141@news.intellij.net...

Hello Chris,

There's a corresponding bug-report in our tracker:
http://youtrack.jetbrains.net/issue/RSRP-259949
and you're welcome to vote for it. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

When I start typing

>

Throw New Arg

>

Instead of being presented with intellisense to select
ArgumentException R# causes full core thrashing for 1 core (perfect
50% cpu usage), ram climbs 50MB~, no answers are returned. When I
finished self typing it eventually R# would stop thrashing, I guess
from bailing on the attempt to auto complete.

>

---
Original message URL:
http://devnet.jetbrains.net/message/5302911#5302911


0

Guest wrote:

Hi Andrew,

you should probably change the status from "fixed" to something else..


You should probably give them a little more credit than that.   It was marked as fixed about half an hour ago...

Will

0

Hello Henning,

It was fixed 40 minutes ago :) Will be in next build.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


HK> Hi Andrew,
HK>
HK> you should probably change the status from "fixed" to something
HK> else..
HK>
HK> Henning
HK>
HK> "Andrew Serebryansky"  wrote in message
HK> news:c8a898dd10e568cddeaf2664b141@news.intellij.net...
HK>
HK> Hello Chris,
HK>
HK> There's a corresponding bug-report in our tracker:
HK> http://youtrack.jetbrains.net/issue/RSRP-259949
HK> and you're welcome to vote for it. Thank you!
HK> Andrey Serebryansky
HK> Senior Support Engineer
HK> JetBrains, Inc
HK> http://www.jetbrains.com
HK> "Develop with pleasure!"
>> When I start typing
>>
>> Throw New Arg
>>
>> Instead of being presented with intellisense to select
>> ArgumentException R# causes full core thrashing for 1 core (perfect
>> 50% cpu usage), ram climbs 50MB~, no answers are returned. When I
>> finished self typing it eventually R# would stop thrashing, I guess
>> from bailing on the attempt to auto complete.
>>
>> ---
>> Original message URL:
>> http://devnet.jetbrains.net/message/5302911#5302911


0

Hi Will,

sorry, didn't saw that.

Kind regards,
Henning

"Will Dean"  wrote in message
news:23850711.77071305204220659.JavaMail.devnet@confluence.jetbrains.net...

Guest wrote:

Hi Andrew,

you should probably change the status from "fixed" to something else..


You should probably give them a little more credit than that.   It was
marked as fixed about half an hour ago...

Will

---
Original message URL: http://devnet.jetbrains.net/message/5302976#5302976

0

Please sign in to leave a comment.