My guess would be that the number of resize events is swamping the event queue.
On Jun 2, 2014, at 7:20 AM, Guillaume Anctil drakk...@gmail.com wrote:
Hi,
I have encountered severe lag in my application when resizing the stage
while an animation is running.
I've made this very simple
It might be something like that. But it seems to be in the platform, not
application related.
When detecting a resize, I tried putting the thread to sleep for a long
amount of time. Something like 5 seconds before adding a new Runnable in
the Platform.runLater queue. It's still very slow when it
You may be hitting this bug: https://javafx-jira.kenai.com/browse/RT-36796
Please try running with -Dprism.order=sw and see if this changes anything.
--
best regards,
Anthony
On 6/2/2014 6:20 PM, Guillaume Anctil wrote:
Hi,
I have encountered severe lag in my application when resizing the
Yes. -Dprism.order=sw does fix the issue. Looking at that bug's sample code
and how to reproduce, it looks very similar.
Thank you. I'll run it in software mode for now and see how bad it affects
performance. I can always apply a hacky workaround of stopping animations
when I detect a resize and
I suggest you add yourself to the bug. At this time, we are not sure
what is causing it. It could be graphics or event queue related as
there is evidence that changing either solves the problem.
Steve
On 2014-06-02, 10:51 AM, Guillaume Anctil wrote:
Yes. -Dprism.order=sw does fix the
We also experienced laggy animation with a stage slide out/down
animation. The animation would change stage size and it appeared to have
only 2 or 3 frames. Workaround was to use a different animation style:
keep stage size but move it 20 px down while changing opacity from low
to full, both
Does running with the software pipeline fix the problem as suggested in
https://javafx-jira.kenai.com/browse/RT-36796 ?
Steve
On 2014-06-02, 11:10 AM, Werner Lehmann wrote:
We also experienced laggy animation with a stage slide out/down
animation. The animation would change stage size and it
Probably not (that code is gone so I don't know for sure). For some
other (Mac-related) reason, the software pipeline was already used for
our internal testing. Didn't seem to make a difference.
FWIW, there was also an NPE occurring if someone was crazy enough to
show that popup many times by
