Very Odd Bug
Jun. 7th, 2006 11:16 am-So, I'm working on this ASP.NET web applicaton. On a particular page, when you click on a item, you sometimes get an error. This bug has some very peculiar behavior.
-The error arises only when the browser is Safari for the Mac, and only when the user is looking at the live site.
-It doesn't happen with the exact same code on the dev site.
-It does happen with assorted iterations of the code, in different locations, using slightly different config files, on the live site.
-It doesn't happen using any other browser we've tested with.
-The text of the error itself is "The data area passed to a system call is too small." This is a Microsoft error, but it's not a terribly specific MS error.
-So. Since it happens with different iterations of the code on the live site, it's a quality of the server that's causing the error. This is reinforced by the fact that code identical to code we're testing on live, when placed on our dev server, doesn't cause the error.
-The error is an MS error, so it's almost certainly not being generated client-side (in Safari on the Mac).
-This could imply that it's happening all the time on the live site, even when we can't see it. When we're using IE as a browser, the error is hidden from us somehow.
-Or, alternately, the data that Safari is sending back to the server is different from what IE sends back, and the difference is causing an MS error.
-Hmm.
-The error arises only when the browser is Safari for the Mac, and only when the user is looking at the live site.
-It doesn't happen with the exact same code on the dev site.
-It does happen with assorted iterations of the code, in different locations, using slightly different config files, on the live site.
-It doesn't happen using any other browser we've tested with.
-The text of the error itself is "The data area passed to a system call is too small." This is a Microsoft error, but it's not a terribly specific MS error.
-So. Since it happens with different iterations of the code on the live site, it's a quality of the server that's causing the error. This is reinforced by the fact that code identical to code we're testing on live, when placed on our dev server, doesn't cause the error.
-The error is an MS error, so it's almost certainly not being generated client-side (in Safari on the Mac).
-This could imply that it's happening all the time on the live site, even when we can't see it. When we're using IE as a browser, the error is hidden from us somehow.
-Or, alternately, the data that Safari is sending back to the server is different from what IE sends back, and the difference is causing an MS error.
-Hmm.