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

active X container crashes on exit with illegal operation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 1.3.0, 1.3.0_01
    • Fix Version/s: 1.3.1_01
    • Component/s: deploy
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      01
    • CPU:
      x86
    • OS:
      windows_95, windows_98
    • Verification:
      Verified

      Backports

        Description

        Appears there is a problem with containers crashing with 1.3.0 and the activeX bridge and the sun.beans.ole.Packager. This did not happen with 1.2.2

        This happens with window 95/98 NT and 2000
        In order to reproduce you will need the BDK1.1 and the 1.3.0 (not the update releases of the 1.3.0_0X as will be explained later)

        You can follow the directions in creating a wrapper at
        http://java.sun.com/products/plugin/1.3/docs/script.html
        (from the c:\program files\javasoft\jre\1.3\ directory run the packager):
        bin\java.exe -cp lib\jaws.jar sun.beans.ole.Packager
        1) Follow the prompts to create the ActiveX control. This will actually be a
        JavaBean that has been "wrapped" by the Sun supplied ActiveX bridge software
        (packager). I have used a variety of jar files from teh BDK1.1/jars directory
        2) Run the ActiveX control in the test container. I have attached one to this bug. TSTCON32.exe

        When you bring up the container, I created a Blue Button from the steps above(in later tests I used juggler and orange button with the same effect), bring up the test container and do an edit-->insert new control and then pick your bean control and then OK.
        It will put the bean in the container.

        Now to crash it simply select file --> exit. When prompted whether to save or not click NO. you will then experience an illegal operation from an invalid page fault in module JVM.DLL

        Now if you clicked YES, it would save and exit. However when you look at the task manager <cntrl> <alt> <del> the TSTCON will still be active. Not sure if this is another bug or related to the crash.

        This behavior of staying active in the task manager is also present in 1.3.1 and update releases of 1.3.0. In these it exits and stays in the task manager and does not crash when selecting the no save option. So at this point it is unsure if the crash problem has been masked or not, but only in the 1.3.0 will it crash.


          Attachments

            Issue Links

              Activity

                People

                Assignee:
                stanleyh Stanley Ho (Inactive)
                Reporter:
                msusko Mark Susko (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: