istinnstudio commented on issue #3962:
URL: https://github.com/apache/netbeans/issues/3962#issuecomment-1677296777

   I get the faulty copy issue 2-3 times a day with FINEST and this is at least 
a pain killer, I am really sorry that there are cases like @bradvido that still 
live with the almost unusable copy/paste state. I would like to sum up the 
fundamental testing conclusions:
   1. The FINEST does not solve the issue for anyone completely, it does 
however "calms down" the frequency of the bug appearance.
   2. The "ghost" copy workaround always solves / resets the state of the 
copy/paste session in any scenario.
   3. @bradvido 's testing code is accurate and always reveals the issue, with 
the FINEST enabled or not. Just use at least 256 iterations to get 1-3 
appearances of the bug if FINEST is being used. Reduce the timing to something 
lower to reduce execution time and repeat if no faulty results. Keep in mind 
that the case where FINEST will not workaround, test code will reveal the issue 
clearly from the first 10 iterations. If the FINEST will act as the "frequency 
reduction workaround" the appearance is random, I estimate an average 
appearance of 1/50  but that is an empirical mixed conclusion from testing with 
the test code and real usage observations. I think that in real life I get the 
bug a little bit sooner and more frequently than the test code, but I cannot be 
sure.
   
   Good luck to the brave contributors.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to