#590 Error: 4 when running

[Matthew D. Hicks]

When I run ProGuard 5.2.1 (Linux, 64-bit, Oracle JDK 1.8.0_65) I get the following output:

[error] Warning: there were 896 unresolved references to classes or interfaces.
[error]          You may need to add missing library jars or update their versions.
[error]          If your code works fine without the missing classes, you can suppress
[error]          the warnings with '-dontwarn' options.
[error]          (http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedclass)
[error] Warning: there were 25 unresolved references to program class members.
[error]          Your input classes appear to be inconsistent.
[error]          You may need to recompile the code.
[error]          (http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedprogramclassmember)
[error] Error: 4

I just assume those warnings are irrelevent to the error 4 but included it just in case. I was previously running out of memory but after increasing to "-Xmx12g" after the last warning it sits for about 15 seconds and just responds with "Error: 4" and exits. If I add "-dontoptimize" it completes successfully, but I want to optimize.

[Eric Lafortune]

"Error: 4" is not something that ProGuard produces -- maybe check your build tool?

12 GB is an unusually large amount of memory -- maybe too much for the computer/OS/VM?

With -verbose, you might get some more details.

You should try to solve the warnings -- cfr. ProGuard manual > Troubleshooting.

[Perry Nguyen]

scala bug, fixed in 2.11.5+, or you can downgrade to proguard 5.0 see #549 and SI-8931

[Perry Nguyen]

(I assume it's a scala thing going by user name)