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.

Sign up for GitHub

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

Jump to bottom

Memory Leak of cgo #72

Open
boobusy opened this issue Feb 13, 2023 · 5 comments
Open

Memory Leak of cgo #72

boobusy opened this issue Feb 13, 2023 · 5 comments
Assignees
@xlab
Labels
investigate

Comments

@boobusy
Copy link

boobusy commented Feb 13, 2023

image

The memory viewing with pprof is very small.
@boobusy boobusy closed this as completed Feb 13, 2023
@xlab
Copy link
Member

xlab commented Feb 13, 2023

@boobusy is it a false alarm?

@boobusy
Copy link
Author

boobusy commented Feb 24, 2023 •
edited
Loading

@xlab
The use of PresentMode = vk.PresentModeImmediate Memory growth is fast.

@xlab xlab reopened this Feb 27, 2023
@xlab xlab self-assigned this Feb 27, 2023
@boobusy
Copy link
Author

boobusy commented Mar 3, 2023

maybe try "github.com/cannibalvox/cgoparam" Memory allocator.

@xlab
Copy link
Member

xlab commented Mar 8, 2023

@boobusy good idea, although I think this would beg for a full rewrite for my cgo generator xD

@akyoto
Copy link

akyoto commented Jun 23, 2024

I stumbled upon this on my Linux machine as well, with PresentMode = vk.PresentModeImmediate you can observe the memory growing very quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xlab xlab

Labels
investigate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@akyoto @xlab @boobusy