JavaFX Performance with Debugger attached

[Scott Palmer]

Just to follow up... I reported this on the NetBeans NetCat list where
Martin Entlicher pointed out the possible issue which I've confirmed.  This
is filed as Issue 241082 in the NetBeans bug tracker.
https://netbeans.org/bugzilla/show_bug.cgi?id=241082

There's a simple workaround for now.

Go to Tools -> Options -> Java -> Java Debugger -> Visual Debugging and
uncheck "Track locations of component hierarchy changes".


Cheers,

Scott


On Fri, Jan 24, 2014 at 7:16 AM, Scott Palmer <swpalmer at gmail.com> wrote:

> Only line breakpoints.  But you are on to something I just did some
> experiments:
>
> If I hit the icon in NetBeans to "Deactivate all breakpoints" it does go
> back to normal. But the Breakpoints window only shows 5 line breakpoints.
>  If I deselect each one manually so none are left active it is still slow.
>  Only when I hit the "deactivate all" button is it responsive.
>
> Perhaps it is a NetBeans bug.. but it is only happening with my FX
> projects.  Maybe I accidentally enabled a field or method breakpoint in the
> JavaFX runtime at some point?
>
> I just deleted all the breakpoints and relaunched - same problem.  And
> still with NO breakpoints defined if I hit the "Deactivate all breakpoints"
> button the performance comes back.
>
> Something's fishy... I'm going to delete my NB cache folder...  nope that
> didn't help... weird. It sounds like this must be a NetBeans issue though.
>  At least when I don't need the breakpoints I have a workaround to speed it
> up.
>
> Thanks,
>
> Scott
>
>
>
> On Thu, Jan 23, 2014 at 8:59 PM, Danno Ferrin <danno.ferrin at oracle.com>wrote:
>
>> What kind of breakpoints do you have set up?   If you have anything other
>> than line and exception breakpoints (such as field or method) then I would
>> expect the VM to crawl like you described.
>>
>>
>> On 1/23/2014 6:43 PM, Scott Palmer wrote:
>>
>>> When I debug my JavaFX application in NetBeans it runs very slow, orders
>>> of
>>> magnitude slower than normal.  Swing apps on the same configuration do
>>> not
>>> have the same problem.
>>>
>>> My guess is that adding and removing Nodes from the Scene is much slower
>>> in
>>> this case, since not all operations are affected.
>>>
>>> For example, I have a TreeView that is filtered on-the-fly as I type in a
>>> search field.  It updates as fast as I can type normally, but under the
>>> debugger each keypress takes a full second or so to appear.
>>>
>>> Has anyone else noticed this phenomenon?
>>>
>>>
>>> Scott
>>>
>>
>>
>