Sometimes the Viewport is damaged. #77910
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
14 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#77910
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Win 10
GTX 1070 - Latest Studio Driver
Blender Version
Broken: Blender 2.90 - Hash:
4db63b6486Worked: Blender 2.83
Short description of error
Viewport is damaged on Startup
Exact steps for others to reproduce the error
Unfortunately the whole thing is not reproducible, sometimes the startup works several times in a row and sometimes I have a damaged viewport several times on start.
Of course I tried it with the default settings.
Same problem.
It should look like this:
But sometimes it looks like this:
or this:
and so on:
Version 290 sub 4 date 2020-06-15 16:49 hash
4db63b6486assign as a type annotation: UV_OT_quad_unwrap.use_linked
assign as a type annotation: EXPORT_OT_svg.render_range
File "e:\Blender-28\2.90\scripts\modules\addon_utils.py", line 382, in enable
mod.register()
File "E:\Blender-28\scripts\addons\Principled-Baker_init_.py", line 124, in register
bpy.types.Scene.principled_baker_combinelist = bpy.props.CollectionProperty(type=PBAKER_CombineListItem)
assign as a type annotation: MESH_OT_optiloops.angle_threshold
assign as a type annotation: MESH_OT_optiloops.only_closed
assign as a type annotation: MESH_OT_optiloops.keep_subsurf_influencing_loops
assign as a type annotation: MESH_OT_optiloops.keep_seams
assign as a type annotation: MESH_OT_optiloops.finish_dissolve
assign as a type annotation: POSELIB_OT_mixcurrpose.influence
assign as a type annotation: POSELIB_OT_mixcurrpose.pose_index
assign as a type annotation: POSELIB_OT_mixedposepaste.influence
assign as a type annotation: MESH_OT_ext_deselect_boundary.keep_cap_edges
assign as a type annotation: MESH_OT_ext_cut_faces.num_cuts
assign as a type annotation: MESH_OT_ext_cut_faces.use_single_edge
assign as a type annotation: MESH_OT_ext_cut_faces.corner_type
assign as a type annotation: MESH_OT_ext_cut_faces.use_grid_fill
assign as a type annotation: GLOBAL_UL_polyshaper_props.local_profile
assign as a type annotation: GLOBAL_UL_polyshaper_props.profile_OBJ
assign as a type annotation: GLOBAL_UL_polysweeper_props.local_profile
assign as a type annotation: GLOBAL_UL_polysweeper_props.profile_OBJ
assign as a type annotation: MESH_OT_z_put_on.turn
assign as a type annotation: UV_OT_z_scale_fragments.axis
assign as a type annotation: SCENE_OT_mscscalmd.sc_clear
assign as a type annotation: SCENE_OT_mscscalmd.sc_dim
assign as a type annotation: CleanCadData.anglelimit
assign as a type annotation: CleanCadData.weldthreshold
assign as a type annotation: CleanCadData.smangle
Added subscriber: @ditos
#80041 was marked as duplicate of this issue
#79746 was marked as duplicate of this issue
#79749 was marked as duplicate of this issue
#79549 was marked as duplicate of this issue
#79228 was marked as duplicate of this issue
#79602 was marked as duplicate of this issue
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
Can you disable all (unofficial) addons and check if you can reproduce this issue?
Hello Richard,
thank you for your request.
Unfortunately I can't understand the problem anymore, because I had to completely reinstall Windows on the weekend.
At the moment I'm in the process of setting up Windows again and then it's Blender's turn.
Unless these are related to the same bug, without context they aren't really useful.
Please edit your comment and upload them as files or delete the wall of text.
In any case get in touch when you will be set up if the issue persists.
Hi Richard,
after the Windows reinstallation not much has improved.
Unfortunately the errors are not reproducible, sometimes Blender Start works 3-4 times in a row, sometimes Blender does not start at all and sometimes the viewport is shot.
All tested only with the standard add-ons.
A particularly "beautiful" specimen:
All crash reports are related to the same error.
Crash from today:
blender.crash.txt
Crashes from the last week:
Crash-1.txt
Crash-2.txt
I always install only the Nvidia core driver, do I need additional modules?
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
I don't think you need to install aditional driver modules here, though I am not Linux user.
?
I am also not a Linux user.
Btw. i'm testing the Blender 2.90.0 Alpha June 23, 23:26:58 -
49234c15e2and haven't even had a shot viewport yet.I hope it stays that way.
Bye and many thanks.
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
Sorry I assumed based on window look. it looked linux-y.
Good to hear this. Can you update us on this in like few days? Will change report state back so we can check. If there will be no issues in 2.90 we would close this report. Some GPU fixes will be backported to 2.83, but not sure if this one as well.
Sure.
Hello, Richard,
as promised, a brief status report.
I'm now at Blender 2.90.0 Alpha June 28, 23:12:10-
b21ba5e579and the Nvidia Studio driver 451.48.The version
b21ba5e579is a deterioration and I have again relatively often shot viewports.With Blender 2.90.0 Alpha June 23, 23:26:58 -
49234c15e2I had much less problems.Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @fclem
Do you have issues with other applications? This do looks like your GPU is broken in some way as we don't have any other report and your configuration is quite standard. Could you try with another GPU (if that is possible)?
Hi Clément,
thank you for inquire.
All other programs run without problems, even a Diva like Davinci Resolve.
I don't think my graphics card is broken, because Blender 2.90.0 Alpha June 23, 23:26:58 -
49234c15e2runs without problems.Then I just have to keep testing, some Blender build will probably work for me again.
Thanks
@ditos I meant program like 3D games or other 3D DCC sofwares. It's likely that the hardware on the GPU used is different between 2D and 3D DCC.
Another thing you can test is running with the
force-workaroundcmd file but we never had anything resolved for an NVidia GPU with that.Do you Overclock your CPU and/or GPU? This might be the cause of the issue if that's the case.
That said, I just found that there is a
Memoryblock GPUVertBuf data: end corruptin your first log (attached to the report). Which might indicate some nasty memory issue but this might be on our end.Can you give us your startup file so we can see if that comes from it? Did you try with factory-startup?
All other programs run without problems, Makehuman, Meshlab, FreeCad, 123D Design etc. Ich have no Games.
No Overclocking on CPU and GPU.
It also occurs (sporadic) without userpref.blend and startup.blend.
Short Test:
Blender.exe --debug-gpu-force-workarounds
Blender starts normal, all is okay.
If I close Blender there is a error message in the console.
Error: Not freed memory blocks: 20, total unfreed memory 0.003700 MB
To conclude the report, here is one last communication.
From version to version it got better.
I'm currently on Blender 2.90.0 Alpha July 10, 23:27:11-
d2b910fafeand have only very rarely a damaged viewport.Many thanks Devs.
Added subscriber: @renderluz-2
I think I have gotten this error, at times I open a file at this happens, the thing is, this is a file I saved yesterday and opened and closed it several times after it was saved, however just now it decided to do this,
Tested on the latest 2.90 build that was made today, my video card is a gtx1080 my OS is Windows10.
And each time I try to open the file the strange exploding looks a bit different just the OP described.
I have loaded the factory settings then saved a new startup file, after that tried to open a file and that seems to have cleared the issue... some how it seems the first file Blender opens i.e. the default startup changes something that can corrupt the next file you try to open after you load Blender, If I can reproduce this error I will send the steps to do so.
Added subscriber: @MarcinTwarowski
Added subscriber: @lichtwerk
Thx @MarcinTwarowski keeping an eye on the duplicate reports.
Since this is the oldest (and @fclem is already involved), lets keep this as the central place to investigate this further.
Added subscribers: @MichelAbassi, @sharaths21312, @Jewls
Added subscribers: @Thane5, @RedMser, @DaveStromberger, @YAFU
Added subscribers: @Pasang, @ZedDB
#79419 (Customshapes broken in Rigigy-Armatures) mentioned that a driver upgrade solved the issue, so maybe we can all give that a go?
It might help if everyone posts again wich card / driver combination they are using, thx.
(I still can reproduce btw., tried multiple builds and opened various files at least ten times without issues -- Nvidia 970m with 440.100 drivers)
Added subscriber: @walt-3
This comment was removed by @walt-3
Here's a video shot in 2.91
21fec95139. I close Blender using alt+f4 for convenience. As you can see it usually takes multiple attempts.visual_glitch_blender291.mp4
Yes that looks exactly like the problem I had, tho the issue seem to go away if just tell Blender to revert to factory settings, then I save that scene as my startup scene, I dont save the preferences after that tho as I still want my settings to remain as they were, all I did was to replace the startup with scene that is more compatible with that version of Blender, after doing that so far I had never encountered this issue again, I think the problem is due to having a startup scene that was created with a different version of Blender, say you created your startup with 2.83 and then updated to 2.83.4 that seems to screw the loading of files for some reason.
for me 2.82-3 files will be displayed like this if they opend with 2.91 or 2.9
Also some files are more unstable and crash more often.
its like @MarcinTwarowski described it.
i can repo with several own files and the bulletkin from #79228.
if you need a really broken file for 2.9 series for tracking it down
CHEST.blend
With this file windows wanted even wipe my hard disk!
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67
Added subscriber: @christian-clavet
Interesting. Yeah, looking at the log, it suffered from a memory corruption error.
IF HARDWARE
To check if there is a memory corruption issue, can you save the project with another name and check if the model is corrupted everytime you load it?
If memory corruption is coming from the ram, it would save the model corrupted, if not and there might have an issue with the VIDEO ram, then the model would only be broken in the viewport. (Render and save ok)
IF SOFTWARE
It also might be a memory leaking issue when streaming the file data while loading. Theses ones are hard to find...
If you have a "debug" build of Blender, it would not crash (but be much slower to run).
Could you check the diff from 23 and 28 of june. Perhaps something introduced such Leaks...
Do you still have this version (june 23) and can you run it again to be sure it still working fine?
This is definitely not a hardware problem. There are many of us having the same problem (corruptions in viewport) simultaneously on different operating systems.
Added subscribers: @mont29, @dfelinto, @ideasman42
Raising awareness to @dfelinto, @ideasman42 , @mont29 that we might have a possible demon lurking around...
(Still unable to reproduce though, but will try more)
@lichtwerk Thats quite wierd. Normally it behaves like this:
2020-08-11 18-58-58.mp4
It looks really similar like what @MarcinTwarowski mentioned but with one diffrence this file crashes on load.
Added subscriber: @Yaroslav-7
Note: I merged #79749 here [which is a bit vague, but shows the same symptoms -- in addition to persistently crashing on going to wireframe (which might help to track down the issue, file provided in #79749)].
So while I am still not able to reproduce, this is reported more than enough, will dare setting this to High priority....
I opened the file in debug mode. It opened correctly. When I switched to wireframe mode it immediately crashed:
blender_debug_output.txt
Another attempt gave slightly different message:
I was able to cause crash when switching to wireframe with this file, but I am not sure if that is the bug we are looking for. I was able to reproduce crash only running release build
a3af59f8e3from MSVC.Unhandled exception at 0x00007FFAEB139229 (ntdll.dll) in blender.exe: 0xC0000374: Stack was corrupted (parameters: 0x00007FFAEB1A27F0).Added subscriber: @Mainman002
Hm I tested this with with 2.91 build by me and the one from the buildbot and with two 2.90 it behaves still the same as shown in the video but NO crash with wireframes.
With 2.80 - 2.83 LTS series no problems appeared.
And with more problematic ancestor builds like 2.7 it had the expected results(nothing to see).
I havent tested it with a debug build because i dont know how to use it correctly but with a little guidance im willing to dig into it.
I cant tell the exact blender version for the Chest file but i think it was 2.81/2 could be also a hint.
I just downloaded the latest build of 2.91 .... blender-2.91.0-275f1039d22c-windows64. Ran it after a fresh reboot of the computer, and I saw the viewport rendering error again. I can create new objects, change lookdev, etc and the problem remains. If I restart Blender, the problem will go away. Seems like it happens after running Blender the first time after a reboot, though I can't say for certain that it hasn't happened at other times. I'm rendering from a 2080 ti.
Here's a screen shot of a UV Sphere that I created.... really wild!
Simply run blender_debug_log.cmd file that you can find inside Blender folder.
Thanks for the advise @MarcinTwarowski With the debug options i cant make it crash on load nor with wireframes.
But I discoverd something else: the chest.blend will always load correctly from within blender independent from the version.
Is there a way to load the file directly into the debug build without the default cube shown up first?
drag and drop doesn't seem to work also "open with" is useless.
Edit: with a debug build it won´t crash on load.
Are we all nvidia users? Anyone with intel or ATI having the problem?
GTX 960 on Linux here. In my case corruption in viewport would seem to be more frequent when you switch between Blender versions interleaved. For example between Blender 2.83 LTS and Blender from buildbot/master
Well the problem is getting bigger.
Does anyone can confirm this?
2020-08-19 04-26-47.mp4
Cant do nothing not even close blender anymore with a damaged file.(restart the pc is the only solution)
this one is interresting its made with 2.91 before the new Geforce driver 452.06
but works well with 2.83. i guess its not driver releated?
Beware flashing lights!
2020-08-19 04-17-00.mp4
Removed subscriber: @christian-clavet
I just downloaded the latest build for 2.91, blender-2.91.0-ce0bcd5fbf40-windows64 and tried to use the cloth brush, I just started Blender, took the default cube, added a multi res and subdivided it a few times then I got some odd square looking artifacts, and the model exploded more less like the way it explodes here.
The latest version of 2.90 blender-2.90.0-05e1ccf10836-windows64 seems to be working fine tho.
Added subscribers: @matteolegna-2, @Udjanii
b'239b0ba7504a' works fine here also.
2020-08-26 16-55-38.mp4
I couldn't reproduce with 2.90
21cb6f09ffnor 2.91396d39c6b9(I was using files F8764149 and F8717837 for testing).Tested with:
2.90.0 commit date: 2020-08-28 14:51, hash:
ddbf41d88d2.91.0 commit date: 2020-08-31 03:47, hash:
6879798202Both look good.
Removed subscriber: @walt-3
So has this been fixed by some intentional specific commit? Or has it been fixed as a side effect of some commit not related to the problem? Perhaps the problem has been fixed by some nvidia driver update?.
I am somewhat confused here. It turns out that Dolphin file manager in KDE can preview the models in .blend files. In some of those .blend files where occasionally there was a corruption problem in viewport, preview image in Dolphin also appeared corrupted. At the moment I cannot reproduce that problem either.
Hopefully we can find out what exactly was causing this strange problem.
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
Then this could be duplicate of #79533 since
263cf2ea94was committed around that time. It says, that it was added to 2.90 but it was merged to master.There are lots of reports merges though and I wasn't really able to reproduce much. So I ask now if anybody does experience these issues?
If there are no problems with latest master (please do specify hash when you respond), I will merge this report.
Added subscriber: @Raimund58
Added subscriber: @forcef
I created #79533 which is perhaps connected to this issue and after devs commited some sort of fix then 2.90 is rock solid for me at least. No more sign of those horrible anomalies and massive crashes/corruptions and so on.
Yes, I was asking people here to check, so I can safely merge these two reports.
Tested with 2.91.0 Alpha, branch: master, commit date: 2020-09-10 21:32, hash:
8ff397b3b1on Win 10 GTX 750 Ti. No issues there.Thanks for info, I will merge these two reports then, if you have problems still after final fix, it would be best to make new report so it is clear that it's different problem.
Closed as duplicate of #79533