Fix/issue 2087 report generation memory leak - #2096
Merged
Dev1822 merged 2 commits intoAug 31, 2026
Merged
Conversation
@Vachhani-Tapan is attempting to deploy a commit to the Dev's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix: Memory Leak in Report Generation Service
Resolves#2087
Description
This PR fixes a critical memory leak that caused Node.js heap exhaustion (OOM/HTTP 502) when generating the Annual Consolidated Payroll Summary for large enterprise tenants.
Previously, the process used
Model.find().lean()to buffer all records into memory synchronously.Code Changes
backend/src/services/reporting.service.jscontaininggenerateAnnualConsolidatedPayrollPDF()..lean()with MongoDB cursors (.cursor()).pdfkit'sPDFDocumentdirectly to the providedoutputStream(e.g., an Expressresobject).for await, rendering them immediately to the PDF stream and discarding them from RAM.Verification