Skip to content
This repository has been archived by the owner on Aug 23, 2020. It is now read-only.

When running a node from a local snapshot that has an old DB an OOM occurs #1474

Open
GalRogozinski opened this issue May 30, 2019 · 3 comments
Open

When running a node from a local snapshot that has an old DB an OOM occurs #1474

GalRogozinski opened this issue May 30, 2019 · 3 comments
Assignees
@DyrellC
Labels
C-Local Snapshots C-Memory T-Bug

Comments

@GalRogozinski
Copy link
Contributor

Bug description

An out of memory error appears when running a node from local snapshot files

IRI version

v1.7.1-RC

Hardware Spec

Hetzner CX51 8-core 32 GB ram
-Xmx 4G

Steps To Reproduce

  1. Take a node that is out of sync
  2. Try to sync it by only copying local snapshot files
  3. Let it sync until an out of memory error appears

Expected behaviour

No errors

Actual behaviour

error

Errors

java.lang.OutOfMemoryError: Java heap space
Dumping heap to java_pid1.hprof ...
@GalRogozinski
Copy link
Contributor Author

GalRogozinski commented Jun 2, 2019 •
edited
Loading

image

This is the analysis of the heap dump. We see that a Thread object is the one holding most of the object.
I suspect that it is the anonymous Thread in LatestMilestoneTrackerImpl becuase it holds a set.
So this is probably related to #1447

@jakubcech jakubcech added the L-Triage Issues that need to be triaged. label Jun 2, 2019
@GalRogozinski GalRogozinski added C-Memory and removed L-Triage Issues that need to be triaged. labels Dec 2, 2019
@GalRogozinski
Copy link
Contributor Author

Related to #1391

@GalRogozinski
Copy link
Contributor Author

Can be fixed by #1447

@DyrellC DyrellC self-assigned this Mar 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DyrellC DyrellC

Labels
C-Local Snapshots C-Memory T-Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jakubcech @GalRogozinski @DyrellC