You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not a duplicate. Before opening a new issue, please search existing issues.
This issue is not a question, feature request, or anything other than a bug report directly related to this project.
Description
When changing from scene with zed stereo rig, Unity reports memory leaks. Fixed by adding OnDestroy method calling OnApplicationQuit() at zed-unity/blob/master/ZEDCamera/Assets/SDK/Helpers/Scripts/Display/ZEDRenderingPlane.cs, wich clears buffer.
Steps to Reproduce
1.Two scnenes, one with stereo camera
2.Change scenes from camera scene
3.Restart playmode and Unity throws leak warning
...
Expected Result
No leaks
Actual Result
Leaks
ZED Camera model
ZED2i
Environment
Win 10
ZED SDK 4.2.0
Anything else?
Added OnDestroy method calling OnApplicationQuit() at zed-unity/blob/master/ZEDCamera/Assets/SDK/Helpers/Scripts/Display/ZEDRenderingPlane.cs, wich clears buffer.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment otherwise it will be automatically closed in 5 days
Preliminary Checks
Description
When changing from scene with zed stereo rig, Unity reports memory leaks. Fixed by adding OnDestroy method calling OnApplicationQuit() at zed-unity/blob/master/ZEDCamera/Assets/SDK/Helpers/Scripts/Display/ZEDRenderingPlane.cs, wich clears buffer.
Steps to Reproduce
1.Two scnenes, one with stereo camera
2.Change scenes from camera scene
3.Restart playmode and Unity throws leak warning
...
Expected Result
No leaks
Actual Result
Leaks
ZED Camera model
ZED2i
Environment
Anything else?
Added OnDestroy method calling OnApplicationQuit() at zed-unity/blob/master/ZEDCamera/Assets/SDK/Helpers/Scripts/Display/ZEDRenderingPlane.cs, wich clears buffer.
The text was updated successfully, but these errors were encountered: