Skip to content

Fix wrong variable in VirtualizedSectionList highlight callback cleanup#56384

Open
Nedunchezhiyan-M wants to merge 1 commit intofacebook:mainfrom
Nedunchezhiyan-M:fix/virtualized-section-list-highlight-cleanup
Open

Fix wrong variable in VirtualizedSectionList highlight callback cleanup#56384
Nedunchezhiyan-M wants to merge 1 commit intofacebook:mainfrom
Nedunchezhiyan-M:fix/virtualized-section-list-highlight-cleanup

Conversation

@Nedunchezhiyan-M
Copy link
Copy Markdown

@Nedunchezhiyan-M Nedunchezhiyan-M commented Apr 8, 2026

Summary

Fix a bug in _setUpdateHighlightFor where the cleanup path deletes from this._updateHighlightFor (which is a method) instead of this._updateHighlightMap (the actual map storing highlight callbacks).

This means highlight callbacks were never cleaned up when cells were removed, causing a memory leak. The $FlowFixMe[prop-missing] annotation was masking what Flow correctly identified as a type error.

For reference, the parallel method _setUpdatePropsFor at line 441 correctly uses this._updatePropsMap for its cleanup path.

Changelog:

[GENERAL] [FIXED] - Fix highlight callback cleanup in VirtualizedSectionList using wrong variable name

Test Plan

  1. Render a SectionList with separator highlight support
  2. Scroll through the list so cells are recycled and removed
  3. Verify that highlight callbacks are properly cleaned up from _updateHighlightMap
  4. Previously, deleting from the method _updateHighlightFor was a no-op, so callbacks accumulated

_setUpdateHighlightFor deletes from this._updateHighlightFor (a method)
instead of this._updateHighlightMap (the actual map). This means
highlight callbacks are never cleaned up when cells are removed,
causing a memory leak. The $FlowFixMe annotation was masking
the type error.
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 8, 2026

Hi @Nedunchezhiyan-M!

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!

@Nedunchezhiyan-M Nedunchezhiyan-M force-pushed the fix/virtualized-section-list-highlight-cleanup branch from d35383c to c2ebc21 Compare April 8, 2026 19:59
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 10, 2026

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

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 10, 2026
@facebook-github-tools facebook-github-tools bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant