Humphrey Clerx

Disabling the specific optimization seems to fix the problem. How can I zoom in on which fields are optimized this way, so I can zoom in on the specific classes in our application that are involved? And what did version 6.2.x change, such that somehow write-only fields can get GC'ed away? On Tue, Dec 17, 2019 at 11:01 AM T. Neidhart tn100@users.sourceforge.net wrote: In order to disable this specific optimization you can add -optimizations !field/removal/writeonly if this is not the cause, you could...

Hello, I will create a ticket, but our application is rather large and it's not easy to pinpoint which exact members get "optimized" in such a way that they are GC'ed away after some time running. Is there any way to prevent these write-only fields to be optimized (i.e. some flag to get back the 6.1.1 behavior)? On Tue, Dec 17, 2019 at 8:16 AM T. Neidhart tn100@users.sourceforge.net wrote: Could you create a ticket at the github project and attach possibly the relevant class files when processed...

After upgrading to ProGuard 6.2.x from 6.1.1 we noticed that some of our applications stopped working correctly after a while. The application runs fine until the first GC (minor and/or major) it seems and then stopped working. It seems that Proguard is optimizing some references/members in such a way that they now become elligible for being cleaned up with GC's. The application runs fine with the same .pro file after being obfuscated/optimized/shrunk with 6.1.1 and doesn't with 6.2.0 and 6.2.2....

UAC elevation doesn't remember setting of wrapper.home

Hi Tim, I've just tested version 4.1.2 and all seems to be OK. Thanks for fixing...

I recompiled Janel using Visual Studio 2015 and was able to get it working on Windows...

When I try to run the latest version of Janel under Windows XP (32-bit), I get an...