Sign in
Microsoft.com
 
Microsoft
 
 
 

none
Unexpected Error and 'shutdown' of IE Window RRS feed

 , 
 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have been leaving a IE v7 window open to this site. On at least three occasions now, after being open for a prolonged period of time (24+ hours), there is an IE 'error' pop-up, and that instance of IE shuts down.

    I will start attempting to capture any error messages and will post them when available.

    You may be only one person in the world, but you may also be the world to one person.
    Monday, February 25, 2008 5:54 AM
    |

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    We've spent a lot of time making sure our javascript doesn't leak. So we're pretty good in IE 7 and firefox but IE 6 definitely has leaking problems itself that are out of our control but due to our frequent client side updates the app will start eating resources.

    We'll have to investigate some options for IE6, perhaps defaulting our auto updates to off for that browser.
    Sam Jarawan STO Forums Senior Development Lead
    Saturday, March 1, 2008 7:05 AM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Me too. After leaving it up for a while, IE becomes unresponsive and I have to manually kill it.
    Phil Brammer | http://www.ssistalk.com
    Monday, February 25, 2008 1:59 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Phil, What version of IE are you using when this happens? I have see you post notes about IE 6 and IE 7.

    Thanks!
    Alicia
    Monday, February 25, 2008 4:19 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    It would be helpful to know whether you are connected to a network or directly to the internet, and if anything shows up in your event logs that would help as well.
    Pam Sallee Program Manager Forums team
    Tuesday, February 26, 2008 11:03 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Alicia Cales said:

    Phil, What version of IE are you using when this happens? I have see you post notes about IE 6 and IE 7.

    Thanks!
    Alicia


    Well, both. IE6 at work. IE7 at home (direct connect). Actually I use FireFox at home more often than not, but when testing certain things, I'll break out IE7 at home. That's why you've seen a myriad of browsers coming from me.

    I actually haven't witnessed a browser crash, but I have witnessed a browser lock-up as a result of these forums. I've had to manually kill it. So the experience is a bit different than Arnie's, but I suspect it's the same root cause. It's always when I leave these forums up for a long period of time. Perhaps a memory leak due to the Ajax calls. Who knows. Now I never leave these forums up; I always navigate away when I'm done reading them.
    Phil Brammer | http://www.ssistalk.com
    Tuesday, February 26, 2008 11:08 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I also experience the lock-up. Leaving the forum open on any page overnight will cause IE 6 to lock hard, end-task is the only option.
    [MVP] http://www.chrisnet.net/code.htm microsoft.public.win32.programmer.directx.audio
    Friday, February 29, 2008 3:52 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    We've spent a lot of time making sure our javascript doesn't leak. So we're pretty good in IE 7 and firefox but IE 6 definitely has leaking problems itself that are out of our control but due to our frequent client side updates the app will start eating resources.

    We'll have to investigate some options for IE6, perhaps defaulting our auto updates to off for that browser.
    Sam Jarawan STO Forums Senior Development Lead
    Saturday, March 1, 2008 7:05 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sam,

    A page just sitting there refreshing itself is not a super important scenario.

    How about we do something like this:

    • If the edit window is closed: after 20 minutes or 100 updates, we reload the whole page instead of doing the background Ajax update.
    • If the edit window is open: after 20 minutes or 100 updates, stop background updates.


    Of course, this requires some additional client-side logic.

    Jeff

    Jeff
    Saturday, March 1, 2008 6:58 PM
    |