Skip to content

Memory Leaks in File and Canvas Handling | Level 3 #54

@ameyvaidya44

Description

@ameyvaidya44

Severity: High

The application creates object URLs (URL.createObjectURL) and canvas elements during file processing but does not consistently clean them up.

Issues include:

Missing URL.revokeObjectURL() calls
Canvas elements not being properly disposed
Accumulation of unused memory over time

Why this matters:
For applications handling large files (e.g., PDFs), memory leaks can quickly degrade performance, causing:

Browser slowdowns
Crashes
Poor user experience, especially on low-memory devices

What’s needed:
Proper lifecycle management:

Revoke object URLs when no longer needed
Clean up canvas resources
Ensure teardown on component unmount

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions