hg: jdk7/tl/jdk: 6805775: LinkedBlockingQueue Nodes should unlink themselves before becoming garbage; ... (original) (raw)
martinrb at google.com martinrb at google.com
Wed Jul 29 00:25:22 UTC 2009
- Previous message: hg: jdk7/tl/jdk: 6785442: ConcurrentLinkedQueue.remove() and poll() can both remove the same element; ...
- Next message: Review request #0: 6863566 (Java should support the freedesktop.org startup notification specification)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Changeset: 49573ab3096a Author: dl Date: 2009-07-28 17:17 -0700 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/49573ab3096a
6805775: LinkedBlockingQueue Nodes should unlink themselves before becoming garbage 6815766: LinkedBlockingQueue's iterator can return null if drainTo(c) executes concurrently Summary: Faster, more correct. Use self-linking trick to avoid gc retention Reviewed-by: martin, dholmes
! src/share/classes/java/util/concurrent/LinkedBlockingDeque.java ! src/share/classes/java/util/concurrent/LinkedBlockingQueue.java ! test/java/util/Collection/MOAT.java
- test/java/util/concurrent/BlockingQueue/OfferDrainToLoops.java
- test/java/util/concurrent/ConcurrentQueues/IteratorWeakConsistency.java
- Previous message: hg: jdk7/tl/jdk: 6785442: ConcurrentLinkedQueue.remove() and poll() can both remove the same element; ...
- Next message: Review request #0: 6863566 (Java should support the freedesktop.org startup notification specification)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]