> > Stopping DisplayLink once we are done with blitting was used to fix > https://bugs.openjdk.org/browse/JDK-8259038 . I think with displayLink active > count as 4 we might see unnecessary(~4) displayLink callbacks when we just > draw text and leave it as noticed in the bug. But i think this tradeoff is > fine as we are trying to achieve balance between power and performance. > > Also this change should not cause state management issues as we are just > maintaining displayLink for longer time. @avu Could you please verify that we > are not seeing issues like https://bugs.openjdk.org/browse/JDK-8247332 ? I’ve checked the scenario from JDK-8247332 - everything works as expected. Best Regards, Alexey > > ------------- > > PR: https://git.openjdk.org/jdk/pull/9512
- RFR: 8290344: Start/stop displaysync affects performance in... Alexey Ushakov
- Re: RFR: 8290344: Start/stop displaysync affects perfo... Ajit Ghaisas
- Re: RFR: 8290344: Start/stop displaysync affects p... Alexey Ushakov
- Re: RFR: 8290344: Start/stop displaysync affects perfo... Phil Race
- Re: RFR: 8290344: Start/stop displaysync affects p... Alexey Ushakov
- Re: RFR: 8290344: Start/stop displaysync affec... Alexey Ushakov
- Re: RFR: 8290344: Start/stop displaysync affects perfo... Alexey Ushakov
- Re: RFR: 8290344: Start/stop displaysync affects p... Ajit Ghaisas
- Re: RFR: 8290344: Start/stop displaysync affects p... Jayathirth D V
- Re: RFR: 8290344: Start/stop displaysync affec... Alexey Ushakov
- Re: RFR: 8290344: Start/stop displaysync affects p... Jayathirth D V
- Integrated: 8290344: Start/stop displaysync affects pe... Alexey Ushakov
