Has anybody noticed timout problems with IWebBrowser2 on CE 4.2 ?

From: jimb (nospam_at_microsurf.net)
Date: 03/16/04 

Date: Tue, 16 Mar 2004 15:57:12 +1100

Has anybody noticed timout problems with IWebBrowser2 on CE 4.2 ?

The reason I ask is because we have been experiencing this problem on our custom
GEODE platform, when leaving a web browser window (created using IWebBrowser2)
unattended for 10 minutes (i.e. 600000 ms), that it will crash the application
it is running in. So we started to isolate the problem;

1. First we ran in Debug mode with everything performing as normal until 10 minutes
    elapses and the folling messages were displayed in the Debug Output window;

        The thread 0x2290C3FA has exited with code 0 (0x0).
        The thread 0xE297D682 has exited with code 0 (0x0).

    Use the browser after these messages will result in;

        Exception 00e Thread=82e16cf8 Proc=42caca82 'Test.exe'
        AKY=00000401 PC=0375267c ESP=1605f434 EA=01f6823c

2. Next, we built the stand alone application using the standard IWebBrowser
    sample code, as per http://msdn.microsoft.com/library/en-us/dnembedded/html/embedded01072003.asp.
    No change in result.

3. Next, we ran it on the Emulator, the only difference was the elapsed time
    it took to timeout, since our emulator was running about twice as slow as
    our realtime equivilant.

4. Now some detailed analysis was required, using the CE Remote Kernel Tracker,
    we observed that 4 threads are created when opening a local html file. Two of
    these threads have 600000 ms timeout values set on a WaitForMultipleObject events.

    When these time-out, the threads are suspended (i.e. migrated to NK.exe).
    Further events to the Web Browser (i.e. clicking on a link) create two new threads,
    however, it seems the parent ControlContainer doesn't know that the previous threads
    have exited and tries to access them directly through the container.
    This results in an Access Violation and crashes the program.

5. We have tried using threads in the background prodding the Browser periodically
    to keep it active, with mixed results.

6. We have built umteen Platforms with a variety of configurations;
    With and without Network, Power Management, and various other suspect components.
    (also as stated above we have targeted differrent platforms).

7. There's many more things we have tried, but above summarises the bulk of it.

We have been on this problem from well over a week, searching high and low for any clues
to the cause of this problem. Only one other posting
(http://groups.google.com.au/groups?q=CE+11.minutes&start=10&hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&safe=active&selm=uWxubpMuCHA.2028%40
TK2MSFTNGP11&rnum=15)
indicates that there may be a timeout problem with IWebBrowser2.

We have run out of ideas here and any help would be greatly appreciated.

Relevant Pages

  • Has anybody noticed timout problems with IWebBrowser2 on CE 4.2 ?
    ... when leaving a web browser window (created using IWebBrowser2) ... these threads have 600000 ms timeout values set on a WaitForMultipleObject events. ... We have built umteen Platforms with a variety of configurations; ...
    (microsoft.public.windowsce.embedded)
  • Has anybody noticed timout problems with IWebBrowser2 on CE 4.2 ?
    ... when leaving a web browser window (created using IWebBrowser2) ... these threads have 600000 ms timeout values set on a WaitForMultipleObject events. ... We have built umteen Platforms with a variety of configurations; ...
    (microsoft.public.windowsce.app.development)
  • Has anybody noticed timout problems with IWebBrowser2 on CE 4.2 ?
    ... when leaving a web browser window (created using IWebBrowser2) ... these threads have 600000 ms timeout values set on a WaitForMultipleObject events. ... We have built umteen Platforms with a variety of configurations; ...
    (microsoft.public.windowsce.embedded.vc)