-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
MacOS m1 excessive memory usage in pass nodes #3612
Comments
Could you quickly check other examples of ours, and also a few |
I forgot to check wgpu for an issue that matches this problem. This Issue exists but it looks to be a frame timing bug. Could be related. I have collected some release mode data, each is the most memory expensive call stack. Edit: Tried to make it more presentable many_spritesWindowed
Borderless
sprite_sheetWindowed
Borderless
3d_sceneWindowed
BorderlessFullscreen
wgpu-mastercube
bunnymark
|
More examples many_cubesWindowed
Borderless
lightingWindowed
Borderless
alien_cake_addictWindowed
Fullscreen
|
We are having the exact same issue: |
The linked issue in wgpu seems to be resolved. Is this still an issue? |
It has been quite some time so I don't have the ability to retest this. From what I remember this was a problem with mac frame management in certain window modes. If wgpu has closed the issue it is probably safe to assume it is no longer a problem in Bevy. |
Bevy version
Bevy 0.6
Operating system & version
MacOS Monterey 12.1
What you did
Profile release and debug of the code from the 3D scene example (this one). The tool I used was the Instruments allocation profiler.
What you expected to happen
My assumption is that a basic example would not use that much memory.
What actually happened
The pass node stack trace show excessive memory usage of about 500mb. In my testing it seems that in release the problem is exaggerated a few times over in to the range of GB.
Just in case I ran it without the profiler and it still uses about 700mb debug and 5gb release according to activity monitor
I am not sure if this a bevy problem or a wgpu problem.
Additional information
Release mode stack trace
Screen cap of pass node calls
I can provide / gather any other data needed
The text was updated successfully, but these errors were encountered: