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

When the number of unresolved async component caches exceeds max set to KeepAlive, nothing is rendered #11427

Closed
kakkokari-gtyih opened this issue Jul 23, 2024 · 4 comments · Fixed by #11496
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: keep-alive

Comments

@kakkokari-gtyih
Copy link
Contributor

kakkokari-gtyih commented Jul 23, 2024

Vue version

v3.5.0-alpha.3, v3.4.34 (Vue SFC Playground)

Link to minimal reproduction

https://play.vuejs.org/#eNrNVN9P2zAQ/ldu2cOK1CYtsJcqVGoRD9vQhlbeCJpMcqWGxLZsJy1C/d93dpysnRhD2steIufuu+8+3w8/R3Ol4qbGaBqlJtdcWTBoazXLBK+U1BaeQeMKdrDSsoIPBP3Qu85lpebBESf+z3EdAhYHgEUAZCKXwrSIS06HM7jJBLSUw+60oNNtB81rrVE4JAkajI8cSZLAJIblhtt8DVaGhHe4khqDPI1Glg2aOBN0s2teoaztYHAEZzN4dokCb9ywskZin2RiN4TJeNynOO5T3LH8scszHwITBTzJGnImqGwIds0sfRBIsSVOA3IVZDASJKSFghtVsics3qxn7PWctnrSpO0S9Yd+LFZEZpH+ANKCN/5Ax5LdYTlLuVA1CXpSeJZFmhVcZhE0o0oWWJIlZCLb1Ccj05h+khnMIU1ajn8lnLSEiz3CQPluNIIlWqjY1pV0AqNRl+0LopqXvEGYkrdlCT7yLmujkIrXW8iWU5GlcOMx5YYCurm6CZJuiSBNelSvwgd3ZYT3K1aWrsd71ORfT2aXki4r7uM4ThP63QtODprQmn5TmCb9hdpOJW2rDmKjoRftN+iFbWQbxi0I3MAVrRM3OBiEyfaTszdKwTyEYzcyb56Z87BefY2mMP+bWL/N/4nYxWtiraGNXPH7+MFIQYL9otG8UjgvUX9TltMbk0XTdgWdjyZBbj57m9U1+jfJx6wxf3zB/mC2zpZFV3Qn1A1mUe+zTN8jrYVzXyy/4pbOvZOWpy4J/Yrzu6tS7TS2sEUtCpK9h/NqP/lXl8b02lxs6f0x3aWcUIfceXwWUddc+/509V9yT+JTH0dPEFXxR4PacVIBT+KP8XjESrVm8Um0+wkHmA1e

Steps to reproduce

(Reproduction was modified from #10899)

  1. Set max to 1 in KeepAlive
    (Set max to a number less than or equal to the number of unresolved asynchronous components)
  2. Switch to CompB before CompA resolves
  3. Switch back to CompA, and you can see that the contents of CompA are not displayed

What is expected?

Expect CompA to be rendered correctly, or start loading again

What is actually happening?

CompA is not rendered when you back from CompB

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
    Memory: 4.31 GB / 15.95 GB
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.2.0 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Chrome: 126.0.6478.182

Any additional comments?

Parent issue: misskey-dev/misskey#14170

@kakkokari-gtyih
Copy link
Contributor Author

Of course setting max to 1 is an extreme case, but it is a problem when max is 2 or more and user switches async components back and forth at high speed.

@kakkokari-gtyih kakkokari-gtyih changed the title #10899 reappears when the number of unresolved async component caches exceeds max set to KeepAlive When the number of unresolved async component caches exceeds max set to KeepAlive, nothing is rendered Jul 24, 2024
@kakkokari-gtyih
Copy link
Contributor Author

Just updated issue title for clarity

@kakkokari-gtyih
Copy link
Contributor Author

Any updates on this?

@edison1105 edison1105 added scope: keep-alive 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. labels Jul 30, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: keep-alive
Projects
None yet
2 participants