Has the move to multi-core CPU's revealed concurrency bugs in your code?
Yes
17% (92 votes)
No
52% (279 votes)
Not sure
31% (170 votes)
Total votes: 541
- Printer-friendly version
- 463 reads
- Login or register to post comments
Comments
little change
by jwenting - 2007-03-25 23:53
We were already running on multi-CPU machines...little change
by mthornton - 2007-03-28 02:54
Ditto, and as a result I have reported several threading related bugs in Java over the years.AWT deadlocked
by linuxhippy - 2007-03-25 15:38
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.
by alexlamsl - 2007-03-24 18:33
"java.util.concurrent" helps ;-)Thanks to Doug et. al.
by jkleemann - 2007-03-30 01:39
but using timeouts on blocking calls left garbage behind(should be fixed in 1.6).Not bugs, but...
by fabriziogiudici - 2007-03-24 09:50
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...
by akarydas - 2007-03-27 23:58
What kind of changes ? Could you please elaborate ?