JidePopup crashes VM

[Gordon]

1. Execute the code included in this post.
2. Click the "Open Popup" button.
3. Click in the JTextfield of the popup to gain focus.
4. Drag the JFrame containing the "Open Popup" button down over the popup.

You may have to try this 2 or 3 times for the VM to crash.

I tried to keep this example as simple as possible.

Code: Select all

@SuppressWarnings("serial")
public class JidePopupDemo extends JFrame {

    public JidePopupDemo() {
        super("JidePopupDemo");
       
        setDefaultCloseOperation(EXIT_ON_CLOSE);
       
        Action openPopup = new AbstractAction("Open Popup") {
            /* (non-Javadoc)
             * @see java.awt.event.ActionListener#actionPerformed(java.awt.event.ActionEvent)
             */
            @Override
            public void actionPerformed(ActionEvent e) {
                JidePopup popup = new JidePopup();
                popup.getContentPane().add(new JTextField("Click here.", 35));
                popup.setFocusable(true);
                popup.showPopup(JidePopupDemo.this);
            }
        };
        add(new JButton(openPopup));
        pack();
    }

    public static void main(String[] args) {
        SwingUtilities.invokeLater(new Runnable() {
            @Override
            public void run() {
                new JidePopupDemo().setVisible(true);
            }
        });
    }

}


My guess is that something down in JidePopup.ancestorMoved() is wreaking havoc, but I haven't dug deep yet.

Here is the exception and I've attached the dump.

Code: Select all

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x010c0136, pid=6252, tid=4152
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) Client VM (16.0-b13 mixed mode windows-x86 )
# Problematic frame:
# C  0x010c0136
#
# An error report file with more information is saved as:
# C:\sandbox\JideSandbox\hs_err_pid6252.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


[JIDE Support]

I tried many times however could not reproduce it. It was tested on Windows Vista, JDK 1.6.0_15 and JIDE release 2.9.0.

Thanks,

[Gordon]

So, Windows XP and JRE version 6.0_18-b07 being the differences. It's not at all difficult to make happen...just a matter of trying a few times. My company is a customer...just trying to track down the POC. At this point, we have to remove all uses of JidePopup from our product unless we can figure this out. Perhaps a video would help reproduce. I'm not sure what else I can do at this point. I don't have a lot of time for diagnosis at the moment.

[JIDE Support]

We have tried on XP, Vista and Windows 7 but couldn't reproduce it. Based on my understanding of EXCEPTION_ACCESS_VIOLATION, it is usually related to hardware. So you probably couldn't reproduce it yourself if you try a different computer. Also sometime rebooting the machine, update driver will fix the issue. And in most cases, we can do nothing about this kind of exception on our API usage level. Even if you want me to write a piece of Java code to throw EXCEPTION_ACCESS_VIOLATION, I don't know how to do it.

Thanks,

[Gordon]

Here is detail on the variation of hardware used:

Dell Latitude 830
XP SP3
NVidia Quatro 140M 11/16/2007 6.14.11.5683

Dell Latitude E6500
Vista SP2
NVidia Quadro NVS 160M 8.16.11.8840 12/14/2009

Dell Latitude E6500
XP SP3
Intel 4 Series Express Chipset Family 10/16/09 6.14.10.5157

Dell Latitude E6500
XP SP3
NVidia Quadro NVS 160M 1/30/09 6.14.11.7947

I've linked this issue to http://bugs.sun.com/bugdatabase/view_bu ... id=6815715.

[JIDE Support]

Maybe for now, you can take a look at JIDE Common Layer's JidePopup and find out which piece of the code is causing the problem. Then try to remove that code (if the consequence is not so bad) or implement a workaround for it. If you let me know the change you make, I will see if I can include the change permanently or build a pre-release for you.

Thanks,