I'm definitely waiting for some bugs to be fixed: the control key not working correctly with copy/paste/arrow keys and the large memory usage with XML files. Copying with Ctrl+C in the other 5.1.2 builds only works one in five times.
Hi, do you have a release plan or similar via youtrack of which bugs you are expected to fix before RS 5 releases halts in favor of RS 6 ?
I cross my fingers for http://youtrack.jetbrains.net/issue/RSRP-183377 , which feels like a "it's easer simply not to use annotations" thing when trying to introduce code annotations usage with the colleagues... Thanks.
At the moment http://youtrack.jetbrains.net/issue/RSRP-195475 is the only issue scheduled for 5.1.2 release. Since we're currently focused on ReSharper 6 development, only really critical bugs will be fixed in ReSharper 5.1.x releases.
Andrey Serebryansky Senior Support Engineer JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!"
Hi, do you have a release plan or similar via youtrack of which bugs you are expected to fix before RS 5 releases halts in favor of RS 6 ?
I cross my fingers for http://youtrack.jetbrains.net/issue/RSRP-183377 , which feels like a "it's easer simply not to use annotations" thing when trying to introduce code annotations usage with the colleagues...
http://youtrack.jetbrains.net/issue/RSRP-196976 is a 'Resharper deletes my source code' bug - I don't know if that counts as 'critical' or not, but I certainly feel prone to criticism when it happens.
"Since we're currently focused on ReSharper 6 development, only really critical bugs will be fixed in ReSharper 5.1.x releases."
I sure wished this was not the case. v5 has not been out that long. There are thousands of bugs filed against it. How can you justify moving on to the next major release with such a buggy present release? My company has fifteen developers and as many licenses for Resharper. Half of the developers refuse to use it because it boggs down their machine so much. And we have nice hardware. The Ctrl key bugs in make the thing nearly unusable for me at present. Just fix bugs in the current release for a while and sell it to make your income. We don't care about adding new features. I just want the features in the present version to work fast and well and without consuming massive memory and CPU resources.
In case this issue gets many votes (which means that it affects many users), we will certainly discuss if this issue can be safely fixed in a bug-fix update. Thank you!
Andrey Serebryansky Senior Support Engineer JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!"
http://youtrack.jetbrains.net/issue/RSRP-196976 is a 'Resharper deletes my source code' bug - I don't know if that counts as 'critical' or not, but I certainly feel prone to criticism when it happens.
I'm afraid I wasn't able to reproduce the problems with CtrlC and CtrlArrows with the latest build of ReSharper 5.1.2 EAP. Do I understand correctly that Ctrl+C starts working fine as soon as you suspend ReSharper (under Tools | Options | ReSharper | General)? As to memory usage with XML files, could you please tell us how big is the XML file, how much memory is consumed by the Visual Studio process with ReSharper enabled and with ReSharper suspended when that file is opened and how big is the managed memory usage reported by ReSharper in the status bar (turn on 'Show managed memory usage' under ReSharper | Options | General)? Thank you!
Andrey Serebryansky Senior Support Engineer JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!"
"Since we're currently focused on ReSharper 6 development, only really critical bugs will be fixed in ReSharper 5.1.x releases."
I sure wished this was not the case. v5 has not been out that long. There are thousands of bugs filed against it. How can you justify moving on to the next major release with such a buggy present release? My company has fifteen developers and as many licenses for Resharper. Half of the developers refuse to use it because it boggs down their machine so much. And we have nice hardware. The Ctrl key bugs in make the thing nearly unusable for me at present. Just fix bugs in the current release for a while and sell it to make your income. We don't care about adding new features. I just want the features in the present version to work fast and well and without consuming massive memory and CPU resources.
The Ctrl+Arrow problem shows up when you have child windows underneath your code window but in the same frame as the code window. Look at the "Messages" window in the attached screenshot. If you don't have a window like that showing, the Ctrl+Arrow keys work fine.
Concerning the Ctrl+C bug (Ctrl+C does nothing four out five times it's pressed) -- I wished that I had a good repro, but I don't. All I can say is that it doesn't work right for me, and it's worse in the 5.1.2.nightlies than it is in 5.0.
The XML memory problem: loading XML files use 10x the memory of the XML file itself. If you load a 100MB XML file, your memory usagle will jump up over a GB. It's not hard to reproduce. I included a test XML file when I filed the bug about it.
The Ctrl+Arrow problem shows up when you have child windows underneath your code window but in the same frame as the code window. Look at the "Messages" window in the attached screenshot. If you don't have a window like that showing, the Ctrl+Arrow keys work fine.
Concerning the Ctrl+C bug (Ctrl+C does nothing four out five times it's pressed) -- I wished that I had a good repro, but I don't. All I can say is that it doesn't work right for me, and it's worse in the 5.1.2.nightlies than it is in 5.0.
The XML memory problem: loading XML files use 10x the memory of the XML file itself. If you load a 100MB XML file, your memory usagle will jump up over a GB. It's not hard to reproduce. I included a test XML file when I filed the bug about it.
I think we should form an international R# bug-voting organisation, where we all frantically vote on each other's bugs, in an attempt to get them taken more seriously by JB.
I have a new theory on the copy/paste issues I was seeing: I think it's caused by a conflict with ReSharper and MS's hotfix KB2251084. More on that after I use it without that hotfix for a few days...
Thank you for this info! Let me know how it goes. Could you please also send me a link to the bug-report that you've filed regargin XML files?
Andrey Serebryansky Senior Support Engineer JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!"
I have a new theory on the copy/paste issues I was seeing: I think it's caused by a conflict with ReSharper and MS's hotfix KB2251084. More on that after I use it without that hotfix for a few days...
We do take all bugs seriously at JB :) 'Voting' is a tool that helps us to find out how many people are affected by the problem (or how many people want a particular feature). If everybody would frantically vote on each other's bugs, we will never get a real picture of the existing problems.
Andrey Serebryansky Senior Support Engineer JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!"
brantheman wrote: > > The Ctrl+Arrow problem shows up when you have child windows underneath > your code window but in the same frame as the code window. Look at the > "Messages" window in the attached screenshot. If you don't have a > window like that showing, the Ctrl+Arrow keys work fine. > > Concerning the CtrlC bug (CtrlC does nothing four out five times > it's pressed) -- I wished that I had a good repro, but I don't. All I > can say is that it doesn't work right for me, and it's worse in the > 5.1.2.nightlies than it is in 5.0. > > The XML memory problem: loading XML files use 10x the memory of the > XML file itself. If you load a 100MB XML file, your memory usagle will > jump up over a GB. It's not hard to reproduce. I included a test XML > file when I filed the bug about it.
I think we should form an international R# bug-voting organisation, where we all frantically vote on each other's bugs, in an attempt to get them taken more seriously by JB.
We do take all bugs seriously at JB :) 'Voting' is a tool that helps us to find out how many people are affected by the problem (or how many people want a particular feature). If everybody would frantically vote on each other's bugs, we will never get a real picture of the existing problems.
I am not completely insensitive to your difficulties, especially when lots of the problems are probably caused by subtle interaction with the endlessly moving target of VS. But I do think you guys should be able to assess a code deletion bug on its own merits, without a need for democracy to spring into action.
You also need to be careful that the bug tracking system doesn't become seen as a mechanism for merely fobbing-off your customers, while you get on with your internal agenda. See MS Connect for a suitably discredited example.
In the last week:
* I've reported a code deletion bug, which was marked as a 'show stopper' by JB staff, but apparently still needs voting before it really actually stops any show (what message does that send either to me or the guy that marked it 'show stopper'?) * I've reported an exception in the 5.1.2 eap which was closed as a dup of an exception that was marked 'obsolete' several years ago. (Huh?)
At least one other (minor) refactoring code gen bug has been endlessly deferred and still exists, unfixed after at least 2 major releases.
But I still like and recommend the product, even if it does get considerably slower and flakier the further one gets from the bits which JB use in-house.
Thank you! We will take a look at both bugs. As a workaround, you can add the big xml file to 'Edit Items to Skip' list under ReSharper | Options | Code Inspection | Settings. On the next Visual Studio start ReSharper will not analyze that file and memory usage will not rise. Let me know if this helps.
Andrey Serebryansky Senior Support Engineer JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!"
Hello John,
We've just published a new build. Thank you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Is 5.1.1757.11 a 5.1.2 build?
Hello Sven
Yes.
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
When is the next build going to be released?
Hello David,
We will release a new build as soon as more issues get fixed for 5.1.2. Are
you waiting for a particular bug to be fixed? Thank you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Not waiting on a particular bug to be fixed. I just wanted to make sure that I hadn't missed an announcement that 5.1.2 had been released already.
I'm definitely waiting for some bugs to be fixed: the control key not working correctly with copy/paste/arrow keys and the large memory usage with XML files. Copying with Ctrl+C in the other 5.1.2 builds only works one in five times.
Hi, do you have a release plan or similar via youtrack of which bugs you are expected to fix before RS 5 releases halts in favor of RS 6 ?
I cross my fingers for http://youtrack.jetbrains.net/issue/RSRP-183377 , which feels like a "it's easer simply not to use annotations" thing when trying to introduce code annotations usage with the colleagues...
Thanks.
I'd like the 'deleting comments' bug fixed if possible: http://youtrack.jetbrains.net/issue/RSRP-196976
Hello,
At the moment http://youtrack.jetbrains.net/issue/RSRP-195475 is the only
issue scheduled for 5.1.2 release. Since we're currently focused on ReSharper
6 development, only really critical bugs will be fixed in ReSharper 5.1.x
releases.
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
http://youtrack.jetbrains.net/issue/RSRP-196976 is a 'Resharper deletes my source code' bug - I don't know if that counts as 'critical' or not, but I certainly feel prone to criticism when it happens.
"Since we're currently focused on ReSharper 6 development, only really critical bugs will be fixed in ReSharper 5.1.x releases."
I sure wished this was not the case. v5 has not been out that long. There are thousands of bugs filed against it. How can you justify moving on to the next major release with such a buggy present release? My company has fifteen developers and as many licenses for Resharper. Half of the developers refuse to use it because it boggs down their machine so much. And we have nice hardware. The Ctrl key bugs in make the thing nearly unusable for me at present. Just fix bugs in the current release for a while and sell it to make your income. We don't care about adding new features. I just want the features in the present version to work fast and well and without consuming massive memory and CPU resources.
Hello Will,
In case this issue gets many votes (which means that it affects many users),
we will certainly discuss if this issue can be safely fixed in a bug-fix
update. Thank you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello,
I'm afraid I wasn't able to reproduce the problems with CtrlC and CtrlArrows
with the latest build of ReSharper 5.1.2 EAP. Do I understand correctly that
Ctrl+C starts working fine as soon as you suspend ReSharper (under Tools
| Options | ReSharper | General)?
As to memory usage with XML files, could you please tell us how big is the
XML file, how much memory is consumed by the Visual Studio process with ReSharper
enabled and with ReSharper suspended when that file is opened and how big
is the managed memory usage reported by ReSharper in the status bar (turn
on 'Show managed memory usage' under ReSharper | Options | General)? Thank
you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
The Ctrl+Arrow problem shows up when you have child windows underneath your code window but in the same frame as the code window. Look at the "Messages" window in the attached screenshot. If you don't have a window like that showing, the Ctrl+Arrow keys work fine.
Concerning the Ctrl+C bug (Ctrl+C does nothing four out five times it's pressed) -- I wished that I had a good repro, but I don't. All I can say is that it doesn't work right for me, and it's worse in the 5.1.2.nightlies than it is in 5.0.
The XML memory problem: loading XML files use 10x the memory of the XML file itself. If you load a 100MB XML file, your memory usagle will jump up over a GB. It's not hard to reproduce. I included a test XML file when I filed the bug about it.
Attachment(s):
badarrowkey.png
I think we should form an international R# bug-voting organisation, where we all frantically vote on each other's bugs, in an attempt to get them taken more seriously by JB.
Will
I have a new theory on the copy/paste issues I was seeing: I think it's caused by a conflict with ReSharper and MS's hotfix KB2251084. More on that after I use it without that hotfix for a few days...
Hello,
Thank you for this info! Let me know how it goes. Could you please also send
me a link to the bug-report that you've filed regargin XML files?
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello Will,
We do take all bugs seriously at JB :) 'Voting' is a tool that helps us to
find out how many people are affected by the problem (or how many people
want a particular feature). If everybody would frantically vote on each other's
bugs, we will never get a real picture of the existing problems.
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
I am not completely insensitive to your difficulties, especially when lots of the problems are probably caused by subtle interaction with the endlessly moving target of VS. But I do think you guys should be able to assess a code deletion bug on its own merits, without a need for democracy to spring into action.
You also need to be careful that the bug tracking system doesn't become seen as a mechanism for merely fobbing-off your customers, while you get on with your internal agenda. See MS Connect for a suitably discredited example.
In the last week:
* I've reported a code deletion bug, which was marked as a 'show stopper' by JB staff, but apparently still needs voting before it really actually stops any show (what message does that send either to me or the guy that marked it 'show stopper'?)
* I've reported an exception in the 5.1.2 eap which was closed as a dup of an exception that was marked 'obsolete' several years ago. (Huh?)
At least one other (minor) refactoring code gen bug has been endlessly deferred and still exists, unfixed after at least 2 major releases.
But I still like and recommend the product, even if it does get considerably slower and flakier the further one gets from the bits which JB use in-house.
I've only filed the two bugs -- one for the XML files and one for the arrow keys. See them here: http://youtrack.jetbrains.net/issues?q=by%3A+Brannon.King
Hello,
Thank you! We will take a look at both bugs. As a workaround, you can add
the big xml file to 'Edit Items to Skip' list under ReSharper | Options |
Code Inspection | Settings. On the next Visual Studio start ReSharper will
not analyze that file and memory usage will not rise. Let me know if this
helps.
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"