[BUG]closeableObject could be closed unsafely in MultiplexProducer.Multiplexer#onNextResult
See original GitHub issuecloseableObject could be closed unsafely in MultiplexProducer.Multiplexer#onNextResult
com.facebook.imagepipeline.producers.MultiplexProducer.Multiplexer#onNextResult
while (iterator.hasNext()) {
Pair<Consumer<T>, ProducerContext> pair = iterator.next();
synchronized (pair) {
pair.first.onNewResult(closeableObject, isFinal);
}
}
The Failed Situation is submitting two image request for the same url image, but their width/height is different. In result, one image request is successful, one image request is failed. e.g.
Here, closeableObject should be cloneOrNull(closeableObject).
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to implement multi-producer multi-consumer single-buffer ...
The following multiple producer multiple consumer single buffer implementation is implemented using Ada. The protected object is the buffer.
Read more >One Producer multiple Consumers - using BlockingQueue
Where a producer will produce items in a commonplace like a Queue. And there are multiple consumers which are processing these records one...
Read more >Multiple producer-multiple consumer queue, Semaphore
... try restarting your device. Your browser can 't play this video. ... Lecture 25: Multiple producer - multiple consumer queue, Semaphore.
Read more >8.3. Producer-Consumer Problem
If there are multiple producers trying to enqueue() data, the mutex ensures that they will not try to manipulate the queue at that...
Read more >L25
However, if there are multiple producers or multiple consumers, this code fails. For example, if two producers try to produce to a full...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@oprisnik Using version 1.0.0 do not have the issues.
Good to know, thanks @huangjunkun