Crash in windows 64 bits about jnativehook

[kwhat]

Can you provide steps or code to duplicating the issue?

[renemeuselwitz]

Sure.

assume the following code:

public class MouseHook
{
/** prints the license terms and turns off logger output
**/
private void printMessage(){
// Clear previous logging configurations.
LogManager.getLogManager().reset();

    // Get the logger for "org.jnativehook" and set the level to off.
    Logger logger =

Logger.getLogger(GlobalScreen.class.getPackage().getName());
logger.setLevel(Level.OFF);
try {
GlobalScreen.registerNativeHook();
GlobalScreen.unregisterNativeHook();
} catch (NativeHookException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}

private void getMouseClick(){
    try{
                    GlobalScreen.registerNativeHook();
        GlobalMouseListener listener = new GlobalMouseListener();
        GlobalScreen.getInstance().addNativeMouseListener(listener);
        while (!listener.isDone()){ /// wait for a click
            Thread.sleep(50);
        }
            NativeMouseEvent mouseEvent = listener.getLastEvent();
       GlobalScreen.unregisterNativeHook();

/// get coordinates
    // do stuff

}
catch (NativeHookException ex) {
System.err.println("There was a problem registering the
native hook.");
System.err.println(ex.getMessage());

            System.exit(1);
    }
    catch (InterruptedException e) {
        e.printStackTrace();
    } catch (AWTException e) {
        e.printStackTrace();
    }

}

}

first I call print message, then getMouseClick. the program exits at
registerNativeHook.
If i don't call printMessage first, it works.
If the program runs in debug mode (eclipse), it also works.

thanks,

René

On 11/11/2014 11:27 AM, Alex Barker wrote:

Can you provide steps or code to duplicating the issue?

—
Reply to this email directly or view it on GitHub
#20 (comment).

[kwhat]

Trunk no longer crashes but it still doesn't behave correctly. Re-registering hooks is causing the jvm to leak threads. Despite calling DetachCurrentThread, native threads are never cleaned up by the jvm O_o

This could be related, I need to do more testing:
http://stackoverflow.com/questions/20325792/java-thread-leaks-when-calling-back-from-native-thread-via-jni
https://bugs.openjdk.java.net/browse/JDK-8033696

[kwhat]

Ok, I have a workaround in place for 1.2.0-RC3. Thanks for the report.