[JIRA] Closed: (MACMULTITOUCH-3) AttachCurrentThread/DetachCurrentThread causes high CPU load on Mac OS X

  • From: "waynekeenan (JIRA)" <jira-no-reply@kenai.com>
  • To: issues@macmultitouch.kenai.com
  • Subject: [JIRA] Closed: (MACMULTITOUCH-3) AttachCurrentThread/DetachCurrentThread causes high CPU load on Mac OS X
  • Date: Mon, 4 Jan 2010 21:20:55 +0000 (GMT+00:00)


     [ 
http://kenai.com/jira/browse/MACMULTITOUCH-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

waynekeenan closed MACMULTITOUCH-3.
-----------------------------------

    Resolution: Won't Fix

perhaps not a bug, but instead an unfortunate side effect of the JNI 
architecture. 

> AttachCurrentThread/DetachCurrentThread causes high CPU load on Mac OS X
> ------------------------------------------------------------------------
>
>                 Key: MACMULTITOUCH-3
>                 URL: http://kenai.com/jira/browse/MACMULTITOUCH-3
>             Project: macmultitouch
>          Issue Type: Bug
>         Environment: Mac OS X 10.5.8, JDK 1.5.0_16
>            Reporter: raner
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The calls to AttachCurrentThread and DetachCurrentThread cause a large 
> number of threads being created and destroyed at a rapid rate. This is an 
> expensive and resource-intensive way of performing callbacks on Mac OS X, 
> and causes a significant increase of the CPU load while the native code is 
> active.
> When run in debug mode from Eclipse, the Eclipse UI can hardly keep up with 
> displaying all the threads that are being created and destroyed as soon as 
> activity from the touchpad is recorded. Also during touchpad movements, the 
> CPU load increases to about 50% of the full capacity of my dual-core system.
> Alternative implementations could be:
> - moving the call to DetachCurrentThread somewhere else (maybe to 
> ..._deregisterListener?), so that subsequent class to AttachCurrentThread 
> effectively become no-ops
> - setting aside a specific Java thread that receives the callbacks and 
> statically storing the JNIEnv for that thread

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://kenai.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Closed: (MACMULTITOUCH-3) AttachCurrentThread/DetachCurrentThread causes high CPU load on Mac OS X

waynekeenan (JIRA) 01/04/2010
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120518.3c65429)
 
 
Close
loading
Please Confirm
Close