OK. What is the impact of the bugs? I haven't noticed any obvious problems when it occurs. Sounds like a GPU resource leak of some kind?
On Tue, Sep 2, 2014 at 6:24 PM, Kevin Rushforth <kevin.rushfo...@oracle.com> wrote: > Ideally we need a reproducible test case with a set of instructions to > demonstrate the bug. I know this can be a challenge for an intermittent bug. > > -- Kevin > > > > Mike Hearn wrote: > > I see this message quite frequently. What sort of things do you need in > these bug reports? > > > On Tue, Sep 2, 2014 at 5:38 PM, Kevin Rushforth < > kevin.rushfo...@oracle.com> wrote: > >> Any time you see this message, it isn't your fault. Rather this is a bug >> in the JavaFX runtime. Please file a JIRA. >> >> -- Kevin >> >> >> >> Mario Ivankovits wrote: >> >>> Hi! >>> >>> Is there anything further I can do to see which resources are locked so >>> I can see if this is my fault and to release them properly? >>> How to interpret this output? >>> >>> Thanks for any info. >>> >>> Outstanding resource locks detected: >>> ES2 Vram Pool: 76.571.592 used (28,5%), 76.571.592 managed (28,5%), >>> 268.435.456 total >>> 118 total resources being managed >>> average resource age is 540,5 frames >>> 57 resources at maximum supported age (48,3%) >>> 6 resources marked permanent (5,1%) >>> 2 resources have had mismatched locks (1,7%) >>> 2 resources locked (1,7%) >>> 79 resources contain interesting data (66,9%) >>> 0 resources disappeared (0,0%) >>> >>> Outstanding resource locks detected: >>> ES2 Vram Pool: 141.193.956 used (52,6%), 141.193.956 managed (52,6%), >>> 268.435.456 total >>> 136 total resources being managed >>> average resource age is 467,8 frames >>> 57 resources at maximum supported age (41,9%) >>> 6 resources marked permanent (4,4%) >>> 5 resources have had mismatched locks (3,7%) >>> 5 resources locked (3,7%) >>> 82 resources contain interesting data (60,3%) >>> 0 resources disappeared (0,0%) >>> >>> >>> Best regards, >>> Mario >>> >> >
