JDK-8099505 : Scene.MouseHandler should be optimized
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx1.2
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2009-03-31
  • Updated: 2015-06-16
  • Resolved: 2010-09-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
fx2.0Resolved
Related Reports
Duplicate :  
Relates :  
Relates :  
Sub Tasks
JDK-8100261 :  
Description
Currently Scene.MouseHandler is called on every pulse, and if there's was a single mouse event, it will continuously go through the list of nodes, doing picking etc, even if the mouse is off the scene.

MouseHandler.process() is the number two allocation spot  in the profiler for the new stack (there's more pressing stuff in the marina stack that's even worse).

To reproduce: run attached app with preset number of nodes (like 2000), move the mouse over the scene, notice that MouseHandler.process() is called even when the mouse is moved from the scene:
 javafx Fire -2000

Comments
the compiler team doesn't have the bandwidth to provide necessary support
09-02-2010

This issue is a duplicates of RT-5475
04-09-2009

This may need to be looked at as part of picking optimizations.
04-09-2009