Skip to content

Fix: Clear correct timeout variable in componentWillUnmount#35815

Open
AmitSingh-5600 wants to merge 1 commit intofacebook:mainfrom
AmitSingh-5600:fix/attribute-behavior-timeout-cleanup
Open

Fix: Clear correct timeout variable in componentWillUnmount#35815
AmitSingh-5600 wants to merge 1 commit intofacebook:mainfrom
AmitSingh-5600:fix/attribute-behavior-timeout-cleanup

Conversation

@AmitSingh-5600
Copy link

Description

Fixed a bug in fixtures/attribute-behavior/src/App.js where the componentWillUnmount lifecycle method was checking for this.timeout but incorrectly attempting to clear this.interval.

Since this.interval is undefined on this component, the actual timeout remained active, leading to potential memory leaks and React "setState" warnings if the timeout fired after the component had unmounted.

Fix

Changed clearTimeout(this.interval) to clearTimeout(this.timeout) to align with the conditional check and the variable used in onMouseEnter.

Related Issues

Closes #35814

Checklist

  • Forked the repository and created a branch from main
  • Run yarn in the repository root
  • Verified the fix in the attribute-behavior fixture

Fixed a bug in fixtures/attribute-behavior/src/App.js where componentWillUnmount
was checking for this.timeout but clearing this.interval (which doesn't exist).

This caused a memory leak where timeouts weren't properly cleaned up on unmount,
and could lead to React warnings about setState on unmounted components.

Changed clearTimeout(this.interval) to clearTimeout(this.timeout) to match
the conditional check and the rest of the component's timeout handling.

Co-authored-by: Cursor <cursoragent@cursor.com>
@meta-cla
Copy link

meta-cla bot commented Feb 18, 2026

Hi @AmitSingh-5600!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla meta-cla bot added the CLA Signed label Feb 18, 2026
@meta-cla
Copy link

meta-cla bot commented Feb 18, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

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.

Bug: Memory leak in attribute-behavior fixture - wrong variable cleared in componentWillUnmount

1 participant

Comments