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

Primevue v4 memory leak problem #5960

Closed
RoyeL12 opened this issue Jun 24, 2024 · 3 comments
Closed

Primevue v4 memory leak problem #5960

RoyeL12 opened this issue Jun 24, 2024 · 3 comments
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted

Comments

@RoyeL12
Copy link

RoyeL12 commented Jun 24, 2024

Describe the bug

Hi there, i just want to let you know there is a memory leak problem server side with primevue v4 for nuxt. Not sure exactly what is causing it but i know it is v4 because the leak disspeared when i downgraded back to v3.56
image

Reproducer

https://stackblitz.com

PrimeVue version

4.0.0

Vue version

3.x

Language

ALL

Build / Runtime

Nuxt

Browser(s)

all

Steps to reproduce the behavior

upgrade to v4 on nuxt

Expected behavior

No response

@RoyeL12 RoyeL12 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jun 24, 2024
@mertsincan
Copy link
Member

Hi @RoyeL12,

Thanks a lot for your screenshot! Could you please create a sample project for us to replicate? Thank you.

@luke-z
Copy link

luke-z commented Jun 25, 2024

might be related to my issue #5957

@mertsincan mertsincan added Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Jun 25, 2024
@mertsincan
Copy link
Member

Duplicate of #5957

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted
Projects
None yet
Development

No branches or pull requests

3 participants