First of all, you need to find the source of the message.
IE is known for providing terrible bug reporting, but fortunately, IE9 seems somewhat capable. If this error occurs in IE6, IE7 or IE8, it will also happen in IE9, so use IE9 for debugging (for your convenience)
Open the webdeveloper console in IE9 (press F12) and follow the steps to get this error.
IE9 should now provide you with information about the file and line in the console, yay!
What usually goes wrong is a callback that is executed after some delay, either with setTimeout or because of an Ajax request. If the window, document or callback frame is defined as unloaded, you will receive this message when it tries to execute your callback function.
Other browsers seem to be ignoring this issue, and I think this is normal. To make IE, do the same, just wrap the callback in a try-catch block (I don't know what the callback will answer for, I don't think it evaluates to undefined). If you want to have more accurate error handling, or if you really want to take action when this happens, you can probably do it, and please post here because I'm curious about which use case will actually require it.
Halcyon
source share