Menu

JavaVM hangs on Mac OSX 64bit after exit

Defects
Anonymous
2014-11-20
2015-02-04
  • Anonymous

    Anonymous - 2014-11-20

    The following is a nuisance and potentially dangerous to the consistency of the databases.
    Xowa runs nicely on Mac OSX 64bit until I hit the exit button.
    Sometimes the java process still hangs - if run from a terminal, I can kill it with Ctrl-C.
    I believe as long as the SWT menu does not come up, or is not used - everything is fine.
    Once the menu is used, the process hangs. Killing it with "killall java" (or similar works).
    BUT: Once I forgot, there was a zombie and a new process - then bad things happened to the next import.
    I can debug more (like attach to the JavaVm ?, if it helps..)
    Thanks
    Markus

     
  • gnosygnu

    gnosygnu - 2014-11-22

    Sorry for the delayed response, and thanks for the report.

    I tried to reproduce but was unable to. For the record, here is my setup and steps:

    • OS X Yosemite
    • Oracle Java 1.8.0_25
    • Ran "sh xowa_macosx_64.sh"
    • Command+Tab until SWT menu is revealed
    • Used the mouse to select Help -> XOWA Help
    • Used the mouse to select File -> Exit
    • Exited to terminal with a $ prompt

    My OS X background is limited, so there may be something else I'm missing. I'll take a closer look later, but if you find anything, it would be helpful

    Thanks!

     
  • Anonymous

    Anonymous - 2015-01-11

    Can't reproduce since 2.1.1.1 (early 2015) -> consider closing.
    Markus

     
  • gnosygnu

    gnosygnu - 2015-01-12

    Cool. Thanks for confirming!

     
  • Anonymous

    Anonymous - 2015-02-02

    The problem can still be reproduced in OS-X unfortunately. If the shell environment is NOT COMPLETE, the hang still happens, however I did not completely analyse the issue.
    I experienced this with wrapping the starting shell script into the OS-X Automator (in order to get a click-able icon), then it did hang. I realized, that the shell did not load the entire environment, which caused the problem. Calling .bash_profile fixed it ....

     
  • gnosygnu

    gnosygnu - 2015-02-04

    Thanks for the report. I'll try this later on an OS X box later this week and post here later.

     

Anonymous
Anonymous

Add attachments
Cancel