Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4238668

suspending thread fails in Windows 98 desktop

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P1 P1
    • 1.2.2
    • 1.2.1, 1.2.2
    • deploy
    • None
    • 1.2.2
    • x86
    • windows_95, windows_nt
    • Not verified


        This is with a Windows 98 vanilla installation with Cricket "S".

        If I use IE to visit a Java plugin enabled page, then exit IE, then
        restart IE and revisit the page, the windows desktop crashes with a
        dialog saying:

             Microsoft Visual C++ Runtime Library

                    Runtime Error!

                    Program: C:\WINDOWS\EXPLORER.EXE

                    abormal program termination


        And then I have to restart the machine. This is *really* bad.

        I can reproduce this consistently. I am seeing it on both my laptop
        and on my test machine under Windows 98.

        The test applet is available at:
        http://zebadee/test/AOL

        I've confirmed that the 1.2.0 plugin/JRE doesn't have this bug.
        So this is something we've added in Cricket.

        graham.hamilton@Eng 1999-05-16

        -----------------------------------------------------------------------

        The plot thickens. Debugging with Visual C++ 6, I have learned that:

        We are getting an abort with a backtrace roughly:
        abort line 43
        panic line 131
        gc0 line 5048
        manageAllocFailutre
        realObjAlloc
        cacheAlloc
        allocArray

        The panic at line 5048 in gc.c is "GC failed to enter single threaded mode"

        Adding some extra aborts in win32 threads_md.c revealed that a call on
        SuspendThread is failing. GetLastError returns 259 which seems bogus.

        The debugger shows that the sys_thread_t we are trying to suspend has a
        thread id of FFFC8E85. The debugger doesmn't list this thread among the
        process's active threads. However it does list this thread as a thread
        that had exited earlier, the first time I exited IE.

        So it looks like (somehow) the list of threads we are manintaing is stale
        and includes at least one thread that has exited.

        graham.hamilton@Eng 1999-05-17

              jdochezorcl Jerome Dochez (Inactive)
              ghamiltosunw Graham Hamilton (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: