Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

I've noticed today that my version of JD-GUI started crashing whenever I tried to open a jar file to decompile. I was on macOS Sierra and had version 0.3.3 of JD-GUI installed. This was the kind of error and crash report I was getting...

Process: jd-gui [13650]
Path: /Applications/JD-GUI.app/Contents/MacOS/jd-gui
Identifier: jd.jd-gui
Version: ???
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: jd-gui [13650]
User ID: 501
Date/Time: 2017-02-21 12:06:45.436 +1000
OS Version: Mac OS X 10.12.3 (16D32)
Report Version: 12
Anonymous UUID: FD4C197F-34C0-7E0B-A88A-B0BDD3397DD7
Sleep/Wake UUID: F6E62B43-7C66-4E90-8968-E92535403845
Time Awake Since Boot: 700000 seconds
Time Since Wake: 320000 seconds
System Integrity Protection: enabled
Crashed Thread: Unknown
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000241499f5
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

Fortunately there was a way to fix it! The latest version (1.4.0 at the time of writing) from the download page fixed the problem.

The latest DMG download also had the same error on launch as my original version, but the TAR download was ok. After doing some reading on the issue it looked to be a problem with JD-GUI needing to be recompiled on the latest Xcode.

I expect the real issue was with Launch4J needing to be updated to work with the latest macOS. Anyway after installing the new version it worked perfectly.


A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. Use of any information from my blog posts should be at own risk and I do not hold any liability towards any information misuse or damages caused by following any of my posts.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
Hi! You can search my blog here ⤵
NOTE: (2022) This Blog is no longer maintained and I will not be answering any emails or comments.

I am now focusing on Atari Gamer.