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

[Bug] Upgrading to 2.0, png image memory usage has doubled, and dcm is normal #1758

Open
David2k13 opened this issue Jan 17, 2025 · 2 comments
Assignees
Labels
bug verified Something isn't working, verified by maintainers

Comments

@David2k13
Copy link
Contributor

Describe the Bug

Upgrading to 2.0, png image memory usage has doubled, and dcm is normal

Steps to Reproduce

1.Upgrading to 2.0
2.check png image

The current behavior

memory usage has doubled

Image
Image

The expected behavior

Memory is normal

OS

macOS 15.1.1

Node version

v20.12.2

Browser

Chrome 131.0.6778.205

Copy link
Member

sedghi commented Jan 22, 2025

What example you are running for this?

@linear linear bot assigned sedghi Jan 24, 2025
@sedghi sedghi added bug verified Something isn't working, verified by maintainers and removed Awaiting Reproduction labels Jan 28, 2025
@sedghi
Copy link
Member

sedghi commented Jan 28, 2025

I can confirm the bug, but after looking really closely, I'm still not sure where it's happening. My guess is that registerWebImageLoader has some kind of reference to the image pixelData or something similar. This type of memory duplication doesn't seem to happen with the other image loaders, so it's pretty specific to the web loader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug verified Something isn't working, verified by maintainers
Projects
None yet
Development

No branches or pull requests

2 participants