# Frequent OutOfMemory and crash after upgrade **URL:** \ **Category:** Sonatype Nexus Repository\ **Tags:** nexus-repository\ **Created:** [July 8, 2020, 4:03pm UTC](https://community.sonatype.com/t/frequent-outofmemory-and-crash-after-upgrade/4580 "2020-07-08T16:03:38Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![joebath](https://avatars.discourse-cdn.com/v4/letter/j/b487fb/32.png) [@joebath](https://community.sonatype.com/u/joebath)\ **Post date:** [July 8, 2020, 4:03pm UTC](https://community.sonatype.com/t/frequent-outofmemory-and-crash-after-upgrade/4580/1 "2020-07-08T16:03:38Z")
We recently upgraded to OSS 3.24.0-02 from 3.20.1-01. Since the upgrade, we’re experiencing frequent crashes related to OutOfMemory. Before upgrading, we were running with 2.5g heap and 2g MaxDirectMemorySize with 8g of physical memory. We’ve since jumped to 4g heap, 17540m MaxDirectMemorySize with 32g of physical memory to try and avoid crashes. We do have verbose GC logging enabled and I did get a heap dump. Here’s what our GC looks like: ![image](https://canada1.discourse-cdn.com/flex047/uploads/communitysonatype/original/2X/a/a6dfcc6f580df8f6ee0fe220a5c48a51b10b09f4.png) From the heap dump, I can see that 94% of our heap is in com.orientechnologies.orient.core.Orient.instance. I’m working on gathering logs and diagnostic data to attach here. Is there anything specific I can provide to help troubleshoot this? ---
**Author:** ![rseddon](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/rseddon/32/341_2.png) [@rseddon](https://community.sonatype.com/u/rseddon)\ **Post date:** [July 8, 2020, 4:19pm UTC](https://community.sonatype.com/t/frequent-outofmemory-and-crash-after-upgrade/4580/2 "2020-07-08T16:19:54Z")
There is one issue that I know of that may be the cause: [https://issues.sonatype.org/browse/NEXUS-24222](https://issues.sonatype.org/browse/NEXUS-24222) This is fixed in the upcoming 3.25.0 release, which will be out soon. Rich