4 ms·
Chances are that your Mac binary is a MacOS package (https://en.m.wikipedia.org/wiki/Package_(macOS) https://en.m.wikipedia.org/wiki/Package_(macOS): “In the Ap
by Someone 6y ago
Chances are that your Mac binary is a MacOS package (https://en.m.wikipedia.org/wiki/Package_(macOS) https://en.m.wikipedia.org/wiki/Package_(macOS): “In the Apple macOS operating system, a package is a file system directory that is normally displayed to the user by the Finder as if it were a single file”)
Right-click the binary and select “Show package contents” to peek inside. Chances are you’ll find a code signature, an icon, various support files, one or more jars and an executable that launches the main jar.
Figuring out what the main jar is typically is easy. You may have to experiment to find out what the current directory has to be when launching it.
- jzer0cool 6y agoAppreciate pointing me in the right direction! Show package contents is exactly what I was looking for. I was looking in the wrong spot before with App Info (cntr + i). Thought I share where I am at: I think I'm in the right direction now. There are log files associated with previous crashes due to out of mem errors. The app here also includes a java vm_param file so I can maybe experiment with a few settings here and hoping here by decreasing the GC recycling time maybe things improve. Also, I will be looking whether the app may have somehow embedded a jvm (possible?) rather than using the one I have provided.