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

Recording seems to trigger a memory leak #92

Open
artyom-zuev opened this issue Jul 30, 2018 · 1 comment
Open

Recording seems to trigger a memory leak #92

artyom-zuev opened this issue Jul 30, 2018 · 1 comment

Comments

@artyom-zuev
Copy link

artyom-zuev commented Jul 30, 2018

What happened?

Whenever recording is enabled, the following four errors repeat in the play mode log:

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

NullReferenceException: Object reference not set to an instance of an object UnityEditor.Recorder.MediaRecorder.RecordFrame (UnityEngine.Recorder.RecordingSession session) (at Assets/Unity Technologies/Recorder/Extensions/MovieRecorder/Recorder/Editor/MediaRecorder.cs:240) UnityEngine.Recorder.RecordingSession.RecordFrame () (at Assets/Unity Technologies/Recorder/Framework/Core/Engine/RecordingSession.cs:131)

A Native Collection has not been disposed, resulting in a memory leak. It was allocated at C:\Work\Unity Projects\PhantomBrigadeCinematics\Assets\Unity Technologies\Recorder\Extensions\MovieRecorder\Audio\Editor\AudioInput.cs:75.

This was not the case in Unity 2018.1.1f1, so this might be caused by some recent engine changes.

Is it reproduceable?

Yes.

Released package version / tag?

Release 0.2 from the Asset Store.

Unity version, operating system, target platform (standalone windows, mac, iOS, PS4...)?

2018.2.1f1

@artyom-zuev
Copy link
Author

artyom-zuev commented Jul 31, 2018

Since its been a very long while since last release but commits continued all this time, this might be something that was already fixed in the repository - in that case, I'd appreciate if someone would point me to a commit where this was fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant