“Artery chokes after 70 copies of Visual Studio”
connect.microsoft.com
“Artery chokes after 70 copies of Visual Studio”
1–10 of 99 posts
Re: “Artery chokes after 70 copies of Visual Studio”
#2What I want to know is this, what hellish workflow led to the discovery of this bug?
Re: “Artery chokes after 70 copies of Visual Studio”
#3Why is this interesting?
Re: “Artery chokes after 70 copies of Visual Studio”
#4What I want to know is this, what hellish workflow led to the discovery of this bug?
My guess would be that it's an automated build / deploy system that required some addon installed to run, so they had to run `devenv /build` instead of using msbuild. Then they saw this behavior on one of their build machines when something wasn't installed correctly and the process just terminated, after 71 retries...
Source: I was on the visual studio environment team a decade ago, and Rube Goldberg himself could not design a build process that would surprise me, at this point.
Re: “Artery chokes after 70 copies of Visual Studio”
#5What I want to know is this, what hellish workflow led to the discovery of this bug?
One main project (open all day) and small projects throughout the week/month with a machine never shut down? I can see that happening easily at web agencies and the like.
Re: “Artery chokes after 70 copies of Visual Studio”
#6What I want to know is this, what hellish workflow led to the discovery of this bug?
One main project (open all day) and small projects throughout the week/month with a machine never shut down? I can see that happening easily at web agencies and the like.
Any more than 5 instances of VS running on one machine gives me pause. I can't imagine going into double-digits, let alone 50+.
I can see 70 files or projects open, but not in VS.
EDIT: Ah, seems I skipped the part where the additional instances are closed.
Re: “Artery chokes after 70 copies of Visual Studio”
#7What I want to know is this, what hellish workflow led to the discovery of this bug?
My guess would be that it's an automated build / deploy system that required some addon installed to run, so they had to run `devenv /build` instead of using msbuild. Then they saw this behavior on one of their build machines when something wasn't installed correctly and the process just terminated, after 71 retries... Source: I was on the visual studio environment team a decade ago, and Rube Goldberg himself could n…
That makes sense... I was imagining that there was some build process that froze VS 99% of the time and some poor developer was sitting at his desk silently crying into his coffee trying over and over to get his project to build so that he can go home for the weekend.
Re: “Artery chokes after 70 copies of Visual Studio”
#8Earlier quoted context omitted.
One main project (open all day) and small projects throughout the week/month with a machine never shut down? I can see that happening easily at web agencies and the like.
Any more than 5 instances of VS running on one machine gives me pause. I can't imagine going into double-digits, let alone 50+. I can see 70 files or projects open, but not in VS. EDIT: Ah, seems I skipped the part where the additional instances are closed.
Step 2 in the reproduction case also includes shutting down the new instance, so I think there is only ever a maximum of two instances at a one time. Seems that the unusual bit is that 70 instances are opened without ever closing the very first instance.
Re: “Artery chokes after 70 copies of Visual Studio”
#9Now that's how bug reports should be written!
Re: “Artery chokes after 70 copies of Visual Studio”
#10hehe.... i wonder if they will fix it or simply accuse you of being an idiot several times over before reading the bug report and realising its genuine. :P
what i find much more interesting than this kind of bug though is that there are several possible ways to expose vs bugs with one step after making a new project in the current version...