OOM - com.bumptech.glide.load.engine.ActiveResources.cleanReferenceQueue (ActiveResources.java:128)

**Glide Version**: 4.11.0

**Integration libraries**:
implementation "com.github.bumptech.glide:glide:4.11.0"
kapt "com.github.bumptech.glide:compiler:4.11.0"

**Device/Android Version**: Vivo 1808 OS 8.1.0

**Issue details / Repro steps / Use case background**: Crash in background

**Stack trace / LogCat**:
```ruby
Fatal Exception: java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack trace available

glide-active-resources
java.lang.Object.wait (Object.java)
java.lang.ref.ReferenceQueue.remove (ReferenceQueue.java:209)
com.bumptech.glide.load.engine.ActiveResources.cleanReferenceQueue (ActiveResources.java:128)
com.bumptech.glide.load.engine.ActiveResources$2.run (ActiveResources.java:61)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
com.bumptech.glide.load.engine.ActiveResources$1$1.run (ActiveResources.java:43)
java.lang.Thread.run (Thread.java:764)
```

Start by reading ActiveResources.java around cleanReferenceQueue at line 128 and review the supplied stack trace. Investigate how the background glide-active-resources thread behaves on the reported Android device and determine whether the OutOfMemoryError can be reproduced. Done requires an identified cause and a verified fix or a documented reason the report cannot be reproduced.

Written by the indexing model from the issue text.