fix: PIL Image Memory Leaks in Dataset Builders #194
+505
−293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During our testing, we found that the memory grows unbounded when processing large datasets, eventually causing OOM errors caused by the PIL Image objects opened during dataset iteration are never closed. Images opened via Image.open() in builders and decoded via Features_Image().decode_example() when loading from parquet accumulate in memory.
So the code changes in this PR add an auto-close PIL Images in as_record_dict() after serialization. Added _close_images()
method to DatasetRecord and DatasetRecordWithPrediction that releases image resources. Also added try/finally blocks in builders (pixparse, funsd, xfund, file_dataset) to close images after local processing.