JDK-4420889 : BEANS.OCX Crashes most MS Office Apps and VC++ Tools
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.3.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2001-03-02
  • Updated: 2002-04-29
  • Resolved: 2002-04-29
Related Reports
Duplicate :  
Description

Name: boT120536			Date: 03/01/2001


C:\>java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

C:\>c:\jre1.3\bin\java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

Using NT 4, SP 5, the Beans.ocx is involved in all of the crashes I've
experienced using just the simple Juggler app provided in the BDK.

In all of the VBA editors of the Office 2000 suite (except PowerPoint), placing
the Packager-created Juggler Bean Control onto a VBA form (all by itself)
causes a crash when attempting to save the form.  In VBA, the Juggler works
fine, until you save the project.

Create a simple form in Excel's VBA editor and place just the Juggler by
itself.  Run the project.  Juggler works fine.  Save the project.  This message
occurs:
EXCEL.EXE - Application Error (the OK/Cancel message box)
The instruction at "0x00000000" referenced memory at "0x00000000". The memory
could not be "read".
Click on OK to terminate the application
Click on CANCEL to debug the application.

Click on debug to have the VC++(6.0) debugger load the app.  In the Context
dropdown (the call stack), the contents are:
00000000()
BEANS! 5013bebc()
02389c8a()
JVM! 504d4eae()
JVM! 5040e87a(), etc...

When using the ActiveX Control Test Container (TSTCON32.EXE), insert the
Juggler control and invoke stopJuggling1 (the method that doesn't take a
parameter).  A VC++ runtime error will occur:
Runtime Error!
  Program: ..Files\Microsoft Visual Studio\Common\Tools\TSTCON32.EXE
abnormal program termination
(Invoking most of the methods (taking no parameters) will produce this error)

Click OK to receive the Application Error dialog which reads:
The instruction at "0x6c371351" referenced memory at "0x00000004".  The memory
could not be "read".
Click on OK to terminate the application.

I also tried a third-party ActiveX container to host the Juggler.  As in the
Office VBA apps, the Juggler runs fine, but when attempting to save the form,
this error occurs:
Application Error
The instruction at "0x5013c500" referenced memory at "0x00000000". The memory
could not be "read".
Click on OK to terminate the application
Click on CANCEL to debug the application

Click on Cancel to load the debugger, and an information message box appears:
Unhandled exception in 3rdpartyapp.exe (BEANS.OCX): 0xC0000005:  Access
Violation.

and the call stack shows:
BEANS! 5013c500()
3rdpartyapp! 0043319f()
MFC42! 6c3eb284()
3rdpartyapp! 00430102()
etc...

Be sure to reboot between crashes.  Occassionally, after the 1st Excel VBA
crash, later instances of Excel VBA will save the form without complaint
thereafter if you don't reboot after the 1st crash.
(Review ID: 117413) 
======================================================================

Comments
EVALUATION The Active-X Bridge was removed in Java 1.4.0 based on a Java Steering Committee decision nearly 2 years ago. The decision was based on 2 things. Customer interest was marginal at best and Java Plug-in was no longer dependent on the bridge technology to operate. It was necessary to remove it to allow for code refactoring and reworking in 1.4.0. Since removing the bridge, many customers have expressed interest in it. We have filed an RFE (4616580) for this support in a future release. We are currently evaluating whether we have a significant business case to justify the 1-3 man-month engineering effort (more for supporting teams) in the Mantis/Tiger timeframe. NOTE: Mantis = Java 1.4.2 FCS Q2, 2003 Tiger = Java 1.5 FCS Q4, 2003 Support for the bridge in existing 1.3.x releases is limited to escalations and can be persued with our CTE team. This bug will be closed as a duplicate of 4616580. ###@###.### 2002-04-29
29-04-2002