ZAP -> Quit (⌘Q) does not properly exit on OS X

[GoogleCodeExporter]

What steps will reproduce the problem?
1. In the OS X native version, go to ZAP -> Quit (⌘Q)

What is the expected output? What do you see instead?
It is expected for ZAP to do a cache commit to the session database.  However, 
it quits immediately without proper handling.

In the logs one sees this, if they do File -> Exit:
10122 [Thread-6] INFO hsqldb.db.HSQLDB379AF3DEBD.ENGINE  - dataFileCache commit 
start
10123 [Thread-6] INFO hsqldb.db.HSQLDB379AF3DEBD.ENGINE  - Database closed
10226 [Thread-6] INFO org.parosproxy.paros.control.Control  - OWASP ZAP 2.3.1 
terminated.

However, this doesn't happen with ZAP -> Quit (⌘Q).

What version of the product are you using? On what operating system?
ZAP 2.3.1, on OS X 10.9.6, using integrated JDK.

Original issue reported on code.google.com by soylentm...@gmail.com on 18 Mar 2015 at 8:32

[GoogleCodeExporter]

Found this thread: 
http://stackoverflow.com/questions/2061194/swing-on-osx-how-to-trap-command-q

Original comment by psii...@gmail.com on 18 Mar 2015 at 8:35

[GoogleCodeExporter]

Agreed.  I also commented on issue 1496, which is related (in that it's about 
unimplemented standard OS X callbacks), but which is more of an enhancement 
instead of a bug.  Feel free to merge if you think they should be.

http://alvinalexander.com/apple/mac/java-mac-native-look/

Really has a long, detailed look at all the steps involved in making a more 
native looking Java application on OS X.

Original comment by soylentm...@gmail.com on 19 Mar 2015 at 12:36

[GoogleCodeExporter]

ZAP has been migrated to github

This issue will be on github issues with the same ID: 
https://github.com/zaproxy/zaproxy/issues

Original comment by psii...@gmail.com on 5 Jun 2015 at 9:18

• Changed state: Done