Skip to content

Conversation

@Ashutosh0x
Copy link

This PR implements disposal logic for CHILD_ENTRY types in on-demand-entry-handler.ts. Previously, these entries were never cleaned up, causing memory leaks in development mode. Fixes #54708

@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: ff048cb

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: ff048cb

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@Ashutosh0x
Copy link
Author

Hi @timneutkens, I've implemented the disposal logic for CHILD_ENTRY types in on-demand-entry-handler.ts. This ensures child entries (like client components) are properly cleaned up when their parent pages are disposed, preventing the memory leak in development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Next.js development high memory usage

2 participants