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
UE4 Hangs/Crashes when updating source control, citing abnormal amounts of GPU usage #86
Comments
I am getting the same issue, but using WWise. An event being renamed, or doing a mass move of files from folder to folder. |
I am suffering with this issue atm any news on a fix? |
This should now be worked around on master with 974ff8f The workaround has been released as part of https://github.com/SRombauts/UE4PlasticPlugin/releases/tag/1.6.1 on the 2nd of August. I am now working on a proper fix to be integrated into Unreal Engine 5.1 |
A similar bug https://issues.unrealengine.com/issue/UE-93603 Directx 12 RHI can run out of video memory on long process (anims import) has been fixed by adding End & BeginFrame on the RHI thread https://github.com/EpicGames/UnrealEngine/commit/4cbce19c2848723ccc01a4fba3133d663d64d4ae |
And the official issue would be https://issues.unrealengine.com/issue/UE-100291 "Out of video memory" crash when attempting to save many assets with source control enabled. A very recent one even mention the workaround I implemented in the plastic plugin! https://issues.unrealengine.com/issue/UE-160299 GPU memory leak during large source control operations:
|
I opened a PR for Epic Games to integrate the proper fix into Unreal Engine 5.1 hopefully: Cheers! |
The proper fix has been submitted to ue5-main https://github.com/EpicGames/UnrealEngine/commit/67dacf2baaafe0d9b6fb5eeb5b179fb5b871a4bf It will be part of UE 5.1 release :) |
…a-space Fix visual diff failing to getfile if there is a space in the path
Result:
UE4 will hang on updating source control and cause abnormal amounts of GPU usage. Might crash editor.
OR
UE4 will now crash if launch with source control enabled. Video of bug available upon request.
The text was updated successfully, but these errors were encountered: