2 ms·
Getting Microsoft to fix bugs is hard. We had a bug in the .Net runtime. Took ages to reach even agreement on the memory dumps: probably because bugs in the .Ne
by zamalek 12y ago
Getting Microsoft to fix bugs is hard. We had a bug in the .Net runtime. Took ages to reach even agreement on the memory dumps: probably because bugs in the .Net runtime are like unicorns, even I had a level of disbelief that .Net was to blame.
Once you prove it, it's completely free. Ultimately memory dumps are the way to go when it comes to MSFT bug reports, if you can catch their bug red-handed and snap it to disk things go real smooth.
- sseveran 12y agoYeah, I found a great one in .net. If you used HttpWebRequest to fetch a url that had an invalid GZIP header the app would hard crash. This is because the request and decompression was being handled on a threadpool thread. An exception would be thrown and no one would be around to catch. Fortunately this was in a web crawler so it took quite a while to build a repro case and an exact diagnoses. I believe it was fixed 4 or 5 years after I reported it in 2008.
- koyote 12y agoHow did you report the bug? I always found it incredibly difficult to report anything to Microsoft and usually only get a 'we have reported it to engineers and it will be fixed some day' message.