History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-25932
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Sergey Coox
Reporter: Oleg Stepanov
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ReSharper

Control+P makes typing extremely slow

Created: 06 Aug 06 18:08   Updated: 09 Sep 06 13:33
Component/s: Parameter Info
Fix Version/s: 2.0.1
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Fixed in build: 251
Old URL: http://www.intellij.net/tracker/resharper/viewSCR?publicId=25932


 Description  « Hide
Hi resharper team!

I have this problem of the slow editor reponse, too and would REALLY LOVE to
have it fixed in one of the next resharper builds.

My machine specs:
CPU: Intel P4 2,66GHz (no hyperthreading)
HDD: 120 GB Seagate ST3120023A
1 GB Ram
Nvidia GeForce4 - 8x Ti 4200 ; 128 Mb Memory

I did the following to find circumstances which affect this performance
bottleneck (without success)

  • deleted every _Resharper directory I could find
  • cleared the Resharper cache from the options dialog.
  • deleted *.suo, *.user
    I didn't try to uninstall Resharper and VS 2003 (I was afraid of loosing all
    my settings)

Then I found all the pdbs and debug info in the released assemblies and
thought "why not give dotTrace a try".
What I did was to fire up my VS 2003 placed the cursor after the open
bracket of a command call (5 parameters).
Then I started the profiler, switched back to VD 2003, pressed CTRL+P and
typed one character ('a'). It took 2 secs until I saw that character - this
was not the slowest one.
The snapshot I took afterwards is attached to this post (Unfortunately I had
to split it into two. the second one comes in a separate post).

Hope that helps. Please try to fix this asap because I can't live without
Resharper.



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.