Sometimes experienced developers make rookie mistakes too
-
Well, I managed to crash Visual Studio 2015 again but the stack trace is, umm, insightful. Application: devenv.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: position at Microsoft.CodeAnalysis.SyntaxNode.FindTokenCore(Int32 position, Boolean findInsideTrivia) at Microsoft.CodeAnalysis.Shared.Extensions.DocumentExtensions.d__2.MoveNext() Stack: at System.Environment.FailFast(System.String, System.Exception) at Microsoft.CodeAnalysis.FailFast.OnFatalException(System.Exception) at Microsoft.CodeAnalysis.ErrorReporting.FatalError.Report(System.Exception, System.Action`1) at Microsoft.CodeAnalysis.ErrorReporting.FatalError.ReportUnlessCanceled(System.Exception) at Microsoft.CodeAnalysis.Shared.Extensions.DocumentExtensions+d__2.MoveNext() at Microsoft.CodeAnalysis.SyntaxNode.FindTokenCore(Int32, Boolean) ... at Microsoft.VisualStudio.Language.Intellisense.Implementation.DefaultCompletionSetPresenter.ShowToolTip() ... at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) We all knew that there were problems lurking in the depths of Intellisense. Now we have proof, ha ha!
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
Well, I managed to crash Visual Studio 2015 again but the stack trace is, umm, insightful. Application: devenv.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: position at Microsoft.CodeAnalysis.SyntaxNode.FindTokenCore(Int32 position, Boolean findInsideTrivia) at Microsoft.CodeAnalysis.Shared.Extensions.DocumentExtensions.d__2.MoveNext() Stack: at System.Environment.FailFast(System.String, System.Exception) at Microsoft.CodeAnalysis.FailFast.OnFatalException(System.Exception) at Microsoft.CodeAnalysis.ErrorReporting.FatalError.Report(System.Exception, System.Action`1) at Microsoft.CodeAnalysis.ErrorReporting.FatalError.ReportUnlessCanceled(System.Exception) at Microsoft.CodeAnalysis.Shared.Extensions.DocumentExtensions+d__2.MoveNext() at Microsoft.CodeAnalysis.SyntaxNode.FindTokenCore(Int32, Boolean) ... at Microsoft.VisualStudio.Language.Intellisense.Implementation.DefaultCompletionSetPresenter.ShowToolTip() ... at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) We all knew that there were problems lurking in the depths of Intellisense. Now we have proof, ha ha!
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
How to file a good bug using Visual Studio Feedback Extension[^] Best Wishes, -David Delaune
Step 12 is missing! That's the one where Microsoft dismisses the bug as not being reproducable and chucks your bug report in the virtual dustbin! :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time -
Step 12 is missing! That's the one where Microsoft dismisses the bug as not being reproducable and chucks your bug report in the virtual dustbin! :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the timeNot all bugs get closed as "not reproducible". Some get closed because "it's too close to the release of vNext, and we're not fixing any more bugs before that". Which would be fine, if they fixed the bugs after the release. But they don't. Because the bug report is closed. So ten versions later, the bug is still present. But if you report it again, it will be too close to the release of vNext+11 for them to consider fixing it. :doh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Not all bugs get closed as "not reproducible". Some get closed because "it's too close to the release of vNext, and we're not fixing any more bugs before that". Which would be fine, if they fixed the bugs after the release. But they don't. Because the bug report is closed. So ten versions later, the bug is still present. But if you report it again, it will be too close to the release of vNext+11 for them to consider fixing it. :doh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
So ten versions later, the bug is still present.
Alternatively they can then dismiss it by (correctly) stating that this bug has already been reported before.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.
