Skip to content

Conversation

@huang-julien
Copy link
Member

πŸ”— Linked issue

resolve #29

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

@danielroe any opinion about this ?

Comment on lines +2 to +7

ref('memory-leak-warning-shown')

export default defineNuxtPlugin(() => {
// Show memory leak warning
})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just for my own understanding - if you wouldn't mind explaining - how does this create a memory leak?
I thought that the ref would be created once and obviously kept in memory, but not consume more memory with subsequent requests.

Isn't it just unsafe in terms of cross-request state pollution?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

usually, when users uses ref outside a vue context, they tends to attach theses references to request events and array and so on.
It's also unsafe in term of XRSP. I admit i had a bit of a tunnel vision here since i'm a bit traumatized by memleaks 🀣

Let's change the wording to XRSP instead. It's way more accurate

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.

feat: server side global ref detection

3 participants