Databases
StackOverflow2013
Postsdbo
POProGuard optimization also remove #wait() calls
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProGuard optimization also remove #wait() calls
    primarykey
    data
    text
    <p>When Proguard optimize my application, it seams that all calls to <code>Object#wait()</code> are being removed.</p> <p>So that each Thread which should passively wait (until notification) is now actively waiting (100% CPU usage).</p> <p>When the optimizing is shutdown with <code>-dontoptimize</code> everything is OK.</p> <p>Has I need the optimization for removing some method with <code>-assumenosideeffects</code>, I am searching for what's wrong.<BR> Is it possible to preserve all calls to <code>Object#wait()</code> to be optimized (removed)?</p> <p>Is there any other solution?</p> <p>EDIT 1: For example this code:</p> <pre><code> @Override public void run() { isRunning = true; try { while (isRunning) { if (parent.isActivate) { parent.updateDriveButtons(); synchronized (this) { wait(1000); } } else { synchronized (this) { // Wait for that the page is activated. Utils.wait(this); } } } } catch (Throwable e) { e.printStackTrace(); } finally { isRunning = false; } } </code></pre> <p>is being replaced by this code (after decompiling the optimized code): <code>wait()</code> has been removed and only the synchronize is visible with <code>monitorenter;</code> ... <code>monitorexit;</code></p> <pre><code> public final void run() { this.isRunning = true; try { while (this.isRunning) { if (this.parent.isShowing()) { ... monitorenter; monitorexit; continue; } monitorenter; monitorexit; }return; } catch (Throwable localThrowable) { Object Ljava/lang/Object;; return; } finally { this.isRunning = false; } throw localObject1; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USarcyqwerty
    1. USelou
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProGuard optimization also remove #wait() calls
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POProGuard optimization also remove #wait() calls
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have a short but complete program that demonstrates the problem? Have you really verified that calls to `wait()` are really being removed? Is it possible that you actually just have some flawed code, and the optimization is just making that flaw more visible?
      singulars
      1. POProGuard optimization also remove #wait() calls
      1. USJon Skeet
    2. COI have added an example which demonstrate this issue
      singulars
      1. POProGuard optimization also remove #wait() calls
      1. USelou
    3. COmonitorenter would already be present due to the synchronized block... so the `wait` call isn't being *replaced* by that. If it's being *removed* then yes, that sounds like a bug. Again, a short but *complete* example (ideally a complete class that can be compiled, then the command line you're using for Proguard) would make life easier for those trying to reproduce the issue.
      singulars
      1. POProGuard optimization also remove #wait() calls
      1. USJon Skeet
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload