Skip to content

Conversation

lfoppiano
Copy link

This PR is a set of attempt to fix a memory leak that happens after a few thousend documents.

The leak is somewhere outside the JVM.

image

(cherry picked from commit 4172805)
(cherry picked from commit 0a5cedd)
…aintain the compatibility with the rest of the processing
# Conflicts:
#	Readme.md
#	src/main/java/org/grobid/core/engines/DataseerClassifier.java
#	src/main/java/org/grobid/core/engines/DatasetParser.java
@lfoppiano lfoppiano force-pushed the bugfix/memory-leak branch from 6857782 to 09c83de Compare April 23, 2025 14:23
@lfoppiano lfoppiano force-pushed the bugfix/memory-leak branch from 09c83de to 8eb8919 Compare April 23, 2025 14:24
# Conflicts:
#	src/main/java/org/grobid/core/engines/DataseerClassifier.java
#	src/main/java/org/grobid/core/utilities/XMLUtilities.java
#	src/main/java/org/grobid/service/controller/DatastetProcessFile.java
#	src/main/java/org/grobid/service/controller/DatastetServiceUtils.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant