Yes, I can confirm this was working on Java 8. Specifically, on 6/4/2019, I upgrade our Jenkins instance from docker jenkins/jenkins:2.164.1 to jenkins/jenkins:2.164.1-jdk11 with active-directory:2.8 to active-directory:2.13. Immediately thereafter, our Jenkins instance started crashing. It took a number of weeks for me diagnose this problem properly, and I subsequently tried upgrading to newer versions of Jenkins and the active-directory plugin. We are now using docker jenkins/jenkins:2.176.1-jdk11 and active-directory:2.16. I finally resolved the issue in our instance by abandoning StartTLS and using LDAPS, as outlined in the plugin documentation.
Memory settings, the VM I was using had 2 cores and 12 GB of RAM initially. I thought the problem was a memory issue, so on 6/11/2019, I changed the VM to 4 cores and 16 GB of RAM, but that didn't make a discernible difference. I found that when I monitored top on the VM (CentOS 7.6), memory usage would never go above 4 GB of RAM, but the virtual memory would grow and grow over time. The highest I saw VIRT was about 28 GB.
Eventually, I installed the plugin monitoring:1.77.0. This allowed me to see the number of open files and threads, which also allowed me to see threads were Waiting and had similar information as what is on this ticket. When I then disabled StartTLS, the symptom went away completely.