OOM in CountingMemoryCache
See original GitHub issueDescription
Taked from user. Just loading images many times. Get stacktrace:
java.lang.OutOfMemoryError: Failed to allocate a 420546432 byte allocation with 25165824 free bytes and 237MB until OOM, max allowed footprint 313199056, growth limit 536870912
at java.util.Arrays.copyOf(Arrays.java:3139)
at java.util.Arrays.copyOf(Arrays.java:3109)
at java.util.ArrayList.grow(ArrayList.java:275)
at java.util.ArrayList.ensureExplicitCapacity(ArrayList.java:249)
at java.util.ArrayList.ensureCapacityInternal(ArrayList.java:241)
at java.util.ArrayList.add(ArrayList.java:467)
at com.facebook.imagepipeline.d.h.a(CountingMemoryCache.java:425)
at com.facebook.imagepipeline.d.h.d(CountingMemoryCache.java:399)
at com.facebook.imagepipeline.d.h.a(CountingMemoryCache.java:198)
at com.facebook.imagepipeline.d.h.a(CountingMemoryCache.java:157)
at com.facebook.imagepipeline.d.o.a(InstrumentedMemoryCache.java:37)
at com.facebook.imagepipeline.k.h$1.a(BitmapMemoryCacheProducer.java:139)
at com.facebook.imagepipeline.k.h$1.a(BitmapMemoryCacheProducer.java:102)
at com.facebook.imagepipeline.k.b.b(BaseConsumer.java:97)
at com.facebook.imagepipeline.k.m$c.a(DecodeProducer.java:368)
at com.facebook.imagepipeline.k.m$c.c(DecodeProducer.java:290)
at com.facebook.imagepipeline.k.m$c.a(DecodeProducer.java:109)
at com.facebook.imagepipeline.k.m$c$1.a(DecodeProducer.java:146)
at com.facebook.imagepipeline.k.v.e(JobScheduler.java:202)
at com.facebook.imagepipeline.k.v.a(JobScheduler.java:22)
at com.facebook.imagepipeline.k.v$1.run(JobScheduler.java:73)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at com.facebook.imagepipeline.e.k$1.run(PriorityThreadFactory.java:51)
at java.lang.Thread.run(Thread.java:764)
Reproduction
In progress
Solution
Not yet
Additional Information
- Fresco version: 1.10.0
- Platform version: 8.1.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
kubelet counts active page cache against memory.available ...
Eventually, the page cache values approached zero. The following is the output of the cgroup's memory.stat about thirty seconds before the OOM.
Read more >MemoryCache OutOfMemoryException - Stack Overflow
MemoryCache has a background thread that periodically estimates how much memory the process is using and how many keys are in the cache....
Read more >Out Of Memory Management - The Linux Kernel Archives
Total page cache as page cache is easily reclaimed; Total free pages because they are already available; Total free swap pages as userspace...
Read more >Intro to In-Memory Caching in C# - YouTube
Application performance is important. Just because your application works in development does not mean it will work well once hundreds of ...
Read more >A large scale analysis of hundreds of in-memory cache ...
Twemcache clusters in cluster count, 26%, 31% and 40% of request rate, cache sizes and CPU cores. 2.4.3 Transient data with no backing...
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
Use guides. Its “one user bug”, will try get heap image before crash.
Hm, I dont get enough info. For now its may be closed.