I’ve been getting these pretty constantly in editor and play mode since moving a project over to the latest 5.4 beta from 5.3.4. I believe error 0x8007000e is related to out of memory but Windows shows I have over 50% of my 16 gigs of memory free and the editor is only using 600-700 megs. Is there some way new to 5.4 to goose it into using more memory or something?
1 Like
Are you using the 64 bit editor?
Can you submit a bug report with the editor logs and list the number here ?
Yep on Windows 10 with an Nvidia 670 on newest drivers. I am trying to reproduce it in a smaller project but so far it only happens in my big one which is a bit much to upload. If it was machine specific I was hoping one of the example projects would trigger it but none of them have so I am slowly adding elements from the main project.
I’m just getting this scrolling in the log
SUCCEEDED(hr)
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 591)
D3D11: Failed to create RenderTexture (1408 x 1058 fmt 9 aa 1), error 0x8007000e
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 282)
D3D11: Failed to create RenderTexture (1408 x 1058 fmt 44 aa 1), error 0x8007000e
Same here in 5.4b21,
D3D11: Failed to create RenderTexture (3076 x 1186 fmt 9 aa 1), error 0x8007000e
Error 0x8007000e means “E_OUTOFMEMORY”. What’s your memory usage when it happens? Are you using 32-bit player?
I am using the 64 bit editor. It comes up when I am trying to inspect objects using UBER shaders’ 4.5b support.
Can we get a bug report?
I’ll try to report it.
I have a similar problem in b22. I’m going to try b23 soon. EDIT: same problem on b23 to!!
This happens if I move my cursor left/right on a spot in the Editor window. I don’t click the mouse…> I just move it left and right. My drivers even crash and I lose power to the monitor to…
Weird.
Never got this error in the editor but have gotten it on all builds since B21. When game goes to load scene, crashes and writes hundreds of these to the crash log.
Machine is 8GB with only about 5GB getting used.
If you have a project where this error can be reproduced with and you have the option to submit it to Unity, I recommend to file a bug-report. If Unity has nothing to reproduce and test their fix against, it’s rather unlikely that they are able to solve this problem.
If you submit a bug-report, make sure to post the case number from the confirmation email here, this allows Unity to pick up your bug-report even faster.
