 |
Has the move to multi-core CPU's revealed concurrency bugs in your code?
| Yes | 17% (92 Votes) | | No | 51.5% (279 Votes) | | Not sure | 31.4% (170 Votes) | Total Votes: 541 |
View Previous Polls
Showing messages 1 through 7 of 7.
-
little change
2007-03-25 22:53:45 jwenting
[Reply | View]
We were already running on multi-CPU machines...
-
little change
2007-03-28 01:54:44 mthornton
[Reply | View]
Ditto, and as a result I have reported several threading related bugs in Java over the years.
-
AWT deadlocked
2007-03-25 14:38:56 linuxhippy
[Reply | View]
I did call setCursor() from another Thread on a java.awt.Panel which deadlocks under XAWT. MAWT and windows work fine anyway - however it should not deadlock especially taking into account that AWT was called thread-safe some years ago ;)
-
Thanks to Doug et. al.
2007-03-24 17:33:57 alexlamsl
[Reply | View]
"java.util.concurrent" helps ;-)
-
Thanks to Doug et. al.
2007-03-30 00:39:52 jkleemann
[Reply | View]
but using timeouts on blocking calls left garbage behind(should be fixed in 1.6).
-
Not bugs, but...
2007-03-24 08:50:54 fabriziogiudici
[Reply | View]
It's almost a year now and I can't recall of bugs - but of course I had to perform changes to take advantage of the second core of my MacBook Pro. I'm talking of GUI apps.
-
Not bugs, but...
2007-03-27 22:58:42 akarydas
[Reply | View]
What kind of changes ? Could you please elaborate ?
|
Showing messages 1 through 7 of 7.
|
|