JavaFX applications turning to "black screen" after some time

[Jerome Cambon]

And I realize you are certainly on Fx 2.2, since although we are working 
hard on it, SB on Fx 8 is not yet avalaible :-)
RT-30362 is specific to Fx 8.0

Using SB 1.1 (so Fx 2.2), I also notice your issue (entirely black 
window) on Win 7 when SB is minimized for a while, then restored.
Generally the window  come back to a normal state after few seconds, 
sometimes more (around 1mn).

I think this deserve a new Jira (for reference), I don't think there is 
one related to that for Fx 2.2.

Thanks
Jerome


On 9/10/13 9:22 AM, John C. Turnbull wrote:
> Hmm, I am not sure that is the same issue.  That issue seems to be related
> to artefacts appearing after screen lock but what I am seeing is a totally
> black window and it doesn't need a locked screen to make it happen.
>
> And at least for me, I have never seen this with Scene Builder although I
> note that you have observed this.
>
> -----Original Message-----
> From: openjfx-dev-bounces at openjdk.java.net
> [mailto:openjfx-dev-bounces at openjdk.java.net] On Behalf Of Jerome Cambon
> Sent: Tuesday, 10 September 2013 17:18
> To: openjfx-dev at openjdk.java.net
> Subject: Re: JavaFX applications turning to "black screen" after some time
>
>
> Seems to be related to this issue:
> https://javafx-jira.kenai.com/browse/RT-30362
>
> And no, unfortunately Scene Builder is not always immune to this, I got it
> with SB regularly
>
> HTH,
> Jerome
>
>
> On 9/10/13 7:55 AM, John C. Turnbull wrote:
>> I am not sure if it is a known issue but any JavaFX application I run
>> and then leave minimised for some time (say 15mins+) and then restore
>> will have an entirely black window with nothing actually visible.
>> This is on Windows
>> 7 and Scene Builder curiously seems to be immune to this problem.
>>
>>    
>>
>> Any ideas why this is happening?  It looks like an off-screen buffer
>> being lost (as it resembles the behaviour I used to see with Swing
>> VolatileImage when the contents were lost)?
>>
>>    
>>
>> Is there any way to programmatically avoid this?
>>
>>    
>>
>> Thanks,
>>
>>    
>>
>> -jct
>>