Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(keep-alive): avoid change reference of keep-alive's vnode on prev… #12987

Closed

Conversation

Yhspehy
Copy link

@Yhspehy Yhspehy commented Mar 18, 2023

fix #12827

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Avoid change reference of keep-alive's vnode on prev _vnode otherwise the new componet's vm will be referenced by older vm.

@yyx990803
Copy link
Member

This isn't the correct fix - see 2632249

@yyx990803 yyx990803 closed this Dec 7, 2023
@Yhspehy Yhspehy deleted the fix(keep-alive)--keep-alive-referenece branch July 19, 2024 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vue2.7 keep-alive removed component no memory free
2 participants