Would the GetLinesFromFile() memory leak cause performance issues on anything outside of this example?
Its hard to think of a broader usecase.
Though I would suppose its annoying that it eats memory on an older machine. But since it will only be updated for VS 2013 that wont matter until the newer machines get old.
Slight affect if doing long running performance testing?
“Artery chokes after 70 copies of Visual Studio”
91–99 of 99 posts
Re: “Artery chokes after 70 copies of Visual Studio”
#92Earlier quoted context omitted.
The issue has already been closed as Fixed.
Based on my experience with connect that doesn't mean it was fixed in the product version you reported it against or any future version.
They mention future version of 2013. So its gone to their bug reports database, to be prioritized rather than is fixed.
Re: “Artery chokes after 70 copies of Visual Studio”
#93Earlier quoted context omitted.
> While an IDE running under Windows is hardly what I would like to work with Visual Studio is probably the best IDE ever created. Have you even used it?
Which other ones have you spent significant time on? : ) IntelliJ is made by the folks that create the resharper plugin that adds decent refactoring to vstudio. Eclipse has equally good refactoring, -out of the box just as IntelliJ
Over the years I have used NetBeans and Eclipse a lot. NetBeans could be beaten for J2ME and was fairly decent for Java web applications. Never really used it for non-web stuff, but it seems reasonable. Eclipse is a complex beast - it's the Emacs of Java (I've jokingly called it Egacs after its tendency to consume all available memory) and is incredibly modular. With that modularity comes complexity and some brittleness. I've used Emacs mostly for Java web application development, but used PyDev for a while. I also used the Eric IDE for Python, but now I write mostly Python and I just use Emacs as my text editor, ipdb (or pdb, when ipdb is not an option - looking at you, Google App Engine) and a couple terminals.
Re: “Artery chokes after 70 copies of Visual Studio”
#94Earlier quoted context omitted.
Yes. I used Visual Studio since 97 (and other Microsoft development tools that eventually merged into VS since 1991). I used VS more than any other development tool until 2001 or 2002. Used it occasionally until 2010. Visual Studio is a very good IDE, but, unless whatever you are developing is designed to run (or be served from) Windows, it's not particularly useful. My problem is not with Visual Studio, but with Win…
We really must be in the age of Linux on the desktop if setting up multiple monitors and printers is trivial...
With Linux, either (a) it works perfectly or (b) you're buggered - there's no in-between.
With Windows, it might work somewhat or with great annoyance. Or it might be lovely! Until Windows rot sets in.
Re: “Artery chokes after 70 copies of Visual Studio”
#95Earlier quoted context omitted.
> The bounty "prize" is you will eventually have a working product to use. While an IDE running under Windows is hardly what I would like to work with, a bug that manifests itself only on such extreme circumstances cannot be called a showstopper. I would worry more about other instances where this Peek() method is being misused like this, perhaps on other situations that happen more frequently than Visual Studio 2013…
> While an IDE running under Windows is hardly what I would like to work with Visual Studio is probably the best IDE ever created. Have you even used it?
I have used it and I have to agree with the grandparent. It is probably one of the worst IDEs I have had to use. Bloated, slow, and in my way even on a modern multicore machine with 8+ gigs of memory.
Of the IDEs I have worked in (Turbo C++ v3.0, Borland C++ v3.1, NetBeans, Eclipse, Rubymine, DrScheme, Turbo Delphi Explorer, RAD Studio XE5, EiffelStudio, GNAT Pro, Visual Studio 6, 2010 and 2013, along with several embedded C environments), Visual Studio is my least favorite. For C++ development on Windows I prefer Eclipse or SublimeText for editing, build using the command line, and debug in WinDbg in order to avoid the awfulness that is the Visual Studio GUI.
Re: “Artery chokes after 70 copies of Visual Studio”
#96Earlier quoted context omitted.
We really must be in the age of Linux on the desktop if setting up multiple monitors and printers is trivial...
With Linux, either (a) it works perfectly or (b) you're buggered - there's no in-between. With Windows, it might work somewhat or with great annoyance. Or it might be lovely! Until Windows rot sets in.
I think Windows rot stopped being a thing since XP. Windows 7 and Windows 8 installations rarely slow down over time, unless you're installing toobars and adware.
Re: “Artery chokes after 70 copies of Visual Studio”
#97Earlier quoted context omitted.
With Linux, either (a) it works perfectly or (b) you're buggered - there's no in-between. With Windows, it might work somewhat or with great annoyance. Or it might be lovely! Until Windows rot sets in.
I think Windows rot stopped being a thing since XP. Windows 7 and Windows 8 installations rarely slow down over time, unless you're installing toobars and adware.
I have a Windows 7 that suffered Windows rot over the year I used it. I finally gave up and went back to the Ubuntu share (despite the Toshiba brightness bug) when Windows refused to suspend properly.
Re: “Artery chokes after 70 copies of Visual Studio”
#98Earlier quoted context omitted.
Based on my experience with connect that doesn't mean it was fixed in the product version you reported it against or any future version.
They mention future version of 2013. So its gone to their bug reports database, to be prioritized rather than is fixed.
From the description of the resolution reasons, that'd be "Deferred".
Re: “Artery chokes after 70 copies of Visual Studio”
#99Earlier quoted context omitted.
They mention future version of 2013. So its gone to their bug reports database, to be prioritized rather than is fixed.
From the description of the resolution reasons, that'd be "Deferred".
I'd imagine deferred, is less "pre-grooming" as "nice-to-have-some-time". But I dont work for MS.