Re: JavaFX Application Heat up MacBook Pro

2016-03-28 Thread Tai Hu
I finally pinpoint the problem with my application. The culprit is ProgressIndicator with undetermined state. There are couple places in my application I used a stack pane to hide a ProgressIndicator at back. Then when I run some task in background thread, I will bring that progress indicator

Re: JavaFX Application Heat up MacBook Pro

2016-03-28 Thread Tai Hu
I launched ensemble8 and go directly to animation example then just leave it there. After few minutes, my Laptop heat up. Tai > On Mar 28, 2016, at 12:06 PM, Tai Hu wrote: > > My MacBook Pro is a i5 dual core with 16GB of memory. The minimal application > that

Re: JavaFX Application Heat up MacBook Pro

2016-03-28 Thread Chien Yang
BTW, I did a 15 min run of Ensemble8 testing a series of programs on my MBP 15 this morning. The machine remains cool and its fan remains off. Can you provide the steps on how you heated up your MBP running Ensemble8? Did you have other programs running? Thanks, - Chien On 3/27/16, 11:37 PM,

Re: JavaFX Application Heat up MacBook Pro

2016-03-28 Thread Tai Hu
My MacBook Pro is a i5 dual core with 16GB of memory. The minimal application that exhibits the issue is just a simple window with web view and I used D3JS draw a simple graph (only 5-6 nodes). Then just let application sit idle there without doing anything. The CPU will heat up quickly. I put

Re: JavaFX Application Heat up MacBook Pro

2016-03-28 Thread Scott Palmer
This must be something else then. How many cores are on the that MacBook? I’m thinking maybe there are four cores and 25% CPU could indicate that there is one thread stuck in a busy loop. That could explain the heat. Do you have any animations running? A static application just sitting there

Re: JavaFX Application Heat up MacBook Pro

2016-03-28 Thread Chien Yang
You are correct. MBP 13 only has an integrated GPU and those 2 fixes mentioned earlier don't apply to your case. - Chien On 3/25/16, 3:15 PM, Tai Hu wrote: I have a MacBook Pro 13 inch (2014 model). If I remembered correctly, it only has an integrated GPU. There is no discreet GPU Thanks,

Re: JavaFX Application Heat up MacBook Pro

2016-03-25 Thread Tai Hu
I have a MacBook Pro 13 inch (2014 model). If I remembered correctly, it only has an integrated GPU. There is no discreet GPU Thanks, Tai On Friday, March 25, 2016, Phil Race wrote: > > > See https://developer.apple.com/library/mac/qa/qa1734/_index.html > It is

Re: JavaFX Application Heat up MacBook Pro

2016-03-25 Thread Phil Race
See https://developer.apple.com/library/mac/qa/qa1734/_index.html It is mentioned in (one of) the bugs you can get to if you follow the JBS bug trail -phil. On 3/25/2016 2:48 PM, Tai Hu wrote: Thanks for the info. What entry should I put into info.plist? Thanks On Friday, March 25, 2016,

Re: JavaFX Application Heat up MacBook Pro

2016-03-25 Thread Tai Hu
Thanks for the info. What entry should I put into info.plist? Thanks On Friday, March 25, 2016, Kevin Rushforth wrote: > Yes, 8u77 has the FX fix for this issue: > > https://bugs.openjdk.java.net/browse/JDK-8132775 > > However, due to the way Apple chose to enable

Re: JavaFX Application Heat up MacBook Pro

2016-03-25 Thread Kevin Rushforth
Yes, 8u77 has the FX fix for this issue: https://bugs.openjdk.java.net/browse/JDK-8132775 However, due to the way Apple chose to enable this, you will need to package your application with the appropriate entry in the Info.plist file. The equivalent AWT fix --

Re: JavaFX Application Heat up MacBook Pro

2016-03-25 Thread Tai Hu
I am on the latest 8u77. On Friday, March 25, 2016, Scott Palmer wrote: > What version of JavaFX are you running? > There is a known issue, where JavaFX (and AWT/Swing) trigger activation of > the discreet GPU. I believe for FX the issue has been resolved in the > latest

Re: JavaFX Application Heat up MacBook Pro

2016-03-25 Thread Scott Palmer
What version of JavaFX are you running? There is a known issue, where JavaFX (and AWT/Swing) trigger activation of the discreet GPU. I believe for FX the issue has been resolved in the latest version, but the equivalent AWT fix hasn't made it to a released version yet. Scott > On Mar 25,