Wirefame , random crash #62030

Closed
opened 2019-02-28 05:25:47 +01:00 by noki paike · 21 comments

System Information
Operating system: Windows 10
Graphics card: Radeon HD 7600m

Blender Version
Broken:
blender-2.80-b1c3d91aed42-win64
Worked:
before the wireframe color builds
...................................................................................
set Wireframe , istant crash.

it does not happen with the default scene with only the cube,
with that I was not able to crash blender by setting the wireframe.

Loading scenes a little bit more complex like mr_helepant, or other, set the wireframe mode and you get instant crash.

This does not always happen,
sometimes do not crash
it's random but the crash happens frequently, and always the same way, selecting wireframe mode

system-info.txt

**System Information** Operating system: Windows 10 Graphics card: Radeon HD 7600m **Blender Version** Broken: blender-2.80-b1c3d91aed42-win64 Worked: before the wireframe color builds ................................................................................... set Wireframe , istant crash. it does not happen with the default scene with only the cube, with that I was not able to crash blender by setting the wireframe. Loading scenes a little bit more complex like mr_helepant, or other, set the wireframe mode and you get instant crash. This does not always happen, sometimes do not crash it's random but the crash happens frequently, and always the same way, selecting wireframe mode [system-info.txt](https://archive.blender.org/developer/F6727780/system-info.txt)
Author

Added subscriber: @nokipaike

Added subscriber: @nokipaike

Added subscriber: @capnm

Added subscriber: @capnm

I don't have any issues here. This was probably fixed, check with the latest build.
bl-wireframe.png

I don't have any issues here. This was probably fixed, check with the latest build. ![bl-wireframe.png](https://archive.blender.org/developer/F6729321/bl-wireframe.png)

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Can't reproduce this either. If it doesn't get solved with a later beta build, you could try and see if it crashes with software rendering to see if this might be a driver issue.
Download this dll and copy it so its located in the same directory as 'blender.exe' and run Blender normally.

Can't reproduce this either. If it doesn't get solved with a later beta build, you could try and see if it crashes with software rendering to see if this might be a driver issue. Download [this dll ](https://download.blender.org/opengl/software-emulation/windows64/opengl32.dll) and copy it so its located in the same directory as 'blender.exe' and run Blender normally.
Author

Added subscribers: @fclem, @mano-wii

Added subscribers: @fclem, @mano-wii
Author

ok guys,
I have tested the same files with the internal gpu intel HD 4000
I can confirm that by starting blender with the same files, I do not have any crashes ... so I suspect there is some mess with the usual buggy amd Radeon HD Drivers for the pre-gcn obsolete gpu
@fclem @mano-wii

ok guys, I have tested the same files with the internal gpu intel HD 4000 I can confirm that by starting blender with the same files, I do not have any crashes ... so I suspect there is some mess with the usual buggy amd Radeon HD Drivers for the pre-gcn obsolete gpu @fclem @mano-wii
Author

@mano-wii I just tested the last build blender-2.80- 490a385c81 -win64

unfortunately your fix fa5950d878 may have improved the situation for some things, but the problem has not been solved, the scenes continue to crash as before

I'll give you this blend file so check yourself
wasp_bo_ottimizzato8.blend

just press the wireframe button with the mouse and instantly crash.

if you open blender and set the wireframe mode, and load one of these scenes (having disabled "loadUI" from the file), blender crash just loads the file.

this particular problem has emerged since the color wireframe was inserted, so I think it's something related to this.

edit:

I suspect it is something that remains in the memory of the GPU even after the crash
with this file I passed you, doing nothing but opening it:

first 2 loop

    • double click on the file,
    • click on wirefrime button: crash

third loop
double click again to start with the file

    • this time will not crash at the firs time set wirframe.
    • solid set
    • wireframe set
  • -set solid
    • set wireframe crash

fourth and fifth loops
crash at first time as the first two loops

fifth time
you have to go wireframe - solid six times before it crash ...

more or les this loops of crash are cyclic.

edit2:

I made a video, which shows that the situation has not changed even for objects based on curves and surfaces .. maybe it takes a lot more because the crash happens, but it happens ..
after an addition of subdivisions blender crash

moreover, but maybe this does not mean anything, I noticed that at each select-click, for a certain number of clicks the memory increases ..
(I also tested the thing with a factory default to prevent it being some addon, and blender behaves the same way)
https://youtu.be/3kUHCSyO5WY

@mano-wii I just tested the last build blender-2.80- 490a385c8124 -win64 unfortunately your fix fa5950d87820 may have improved the situation for some things, but the problem has not been solved, the scenes continue to crash as before I'll give you this blend file so check yourself [wasp_bo_ottimizzato8.blend](https://archive.blender.org/developer/F6740610/wasp_bo_ottimizzato8.blend) just press the wireframe button with the mouse and instantly crash. if you open blender and set the wireframe mode, and load one of these scenes (having disabled "loadUI" from the file), blender crash just loads the file. this particular problem has emerged since the color wireframe was inserted, so I think it's something related to this. edit: I suspect it is something that remains in the memory of the GPU even after the crash with this file I passed you, doing nothing but opening it: **first 2 loop** - - double click on the file, - - click on wirefrime button: crash **third loop** double click again to start with the file - - this time will not crash at the firs time set wirframe. - - solid set - - wireframe set - -set solid - - set wireframe crash **fourth and fifth loops** crash at first time as the first two loops **fifth time** you have to go wireframe - solid six times before it crash ... more or les this loops of crash are cyclic. edit2: I made a video, which shows that the situation has not changed even for objects based on curves and surfaces .. maybe it takes a lot more because the crash happens, but it happens .. after an addition of subdivisions blender crash moreover, but maybe this does not mean anything, I noticed that at each select-click, for a certain number of clicks the memory increases .. (I also tested the thing with a factory default to prevent it being some addon, and blender behaves the same way) https://youtu.be/3kUHCSyO5WY

Removed subscriber: @capnm

Removed subscriber: @capnm

Added subscriber: @ideasman42

Added subscriber: @ideasman42

I was able to reproduce the crash. I'll investigate;

On the increase in memory, it should be related to the UNDO system. But I'm not sure.
Maybe @ideasman42 knows what that is.

I was able to reproduce the crash. I'll investigate; On the increase in memory, it should be related to the UNDO system. But I'm not sure. Maybe @ideasman42 knows what that is.
Author

also with the attempt to fix ae977d13f8 the situation has remained unchanged, blender continues to crash with the wireframe mode ...
it seems that the more you have wireframes in the buffer, the more chance you have of a crash

also with the attempt to fix ae977d13f8e9 the situation has remained unchanged, blender continues to crash with the wireframe mode ... it seems that the more you have wireframes in the buffer, the more chance you have of a crash
Author

@mano-wii
I have done other digging work:
on all heavy scenes like mr_elephant, wasp_bot, wanderer, all crashing scenes, if I select all objects and enter edit mode, there is no way to crash blender, switching from wireframe mode to solid mode ...

then I did, always with all the selected objects, a remove doubles ... and also a "make normal consistent"

and I discovered this:

wasp_bot scenes no longer crash, there is no way to make it crash.

mr_elephant is more stable but sametimes crash

wanderer I do not know if it's improved but it keeps crashing ..

the two scenes, wanderer and mr_elephant have problems of normal flipped in some points ...

I also discovered maybe another bug on wanderer:
selecting all the objects, entering edit mode, selecting all, selecting all the points, but pressing "deselect all", some objects remain with their selected points, and there is no way to deselect them, even by pressing several times select all and deselect all

Screenshot (45).jpg

Screenshot (46).jpg

Screenshot (42).jpg

Screenshot (44).jpg

Screenshot (43).jpg

@mano-wii I have done other digging work: on all heavy scenes like mr_elephant, wasp_bot, wanderer, all crashing scenes, if I select all objects and enter edit mode, there is no way to crash blender, switching from wireframe mode to solid mode ... then I did, always with all the selected objects, a remove doubles ... and also a "make normal consistent" and I discovered this: wasp_bot scenes no longer crash, there is no way to make it crash. mr_elephant is more stable but sametimes crash wanderer I do not know if it's improved but it keeps crashing .. the two scenes, wanderer and mr_elephant have problems of normal flipped in some points ... I also discovered maybe another bug on wanderer: selecting all the objects, entering edit mode, selecting all, selecting all the points, but pressing "deselect all", some objects remain with their selected points, and there is no way to deselect them, even by pressing several times select all and deselect all ![Screenshot (45).jpg](https://archive.blender.org/developer/F6753509/Screenshot__45_.jpg) ![Screenshot (46).jpg](https://archive.blender.org/developer/F6753500/Screenshot__46_.jpg) ![Screenshot (42).jpg](https://archive.blender.org/developer/F6753501/Screenshot__42_.jpg) ![Screenshot (44).jpg](https://archive.blender.org/developer/F6753503/Screenshot__44_.jpg) ![Screenshot (43).jpg](https://archive.blender.org/developer/F6753511/Screenshot__43_.jpg)
Author

and I found out that multicolor in edit mode (by selecting all objects) is not working ... and that's probably what does not make blender crash in wireframe in edit mode ... because I just get out of edit mode blender crash

Screenshot (47).jpg

and I found out that multicolor in edit mode (by selecting all objects) is not working ... and that's probably what does not make blender crash in wireframe in edit mode ... because I just get out of edit mode blender crash ![Screenshot (47).jpg](https://archive.blender.org/developer/F6753685/Screenshot__47_.jpg)
Author

@mano-wii Nice Strike man!

not only is blender now as solid as a rock ...

but in heavy scenes, now the gpu feels that it works more (the fan will turn faster to cool)

soo...there's more:

the scenes are much more reactive also in EEVEE, with the volumetric functions activated that without ... and even in edit mode it responds more quickly!

trust me, I do these tests every day, I know what I'm talking about ...
I made a video ...
https://youtu.be/OMuuKst532k
I would say problem solved obviously ..

@mano-wii Nice Strike man! not only is blender **now as solid as a rock** ... but in heavy scenes, now the gpu feels that it works more (the fan will turn faster to cool) soo...there's more: ``` the scenes are much more reactive also in EEVEE, with the volumetric functions activated that without ... and even in edit mode it responds more quickly! ``` trust me, I do these tests every day, I know what I'm talking about ... I made a video ... https://youtu.be/OMuuKst532k I would say problem solved obviously ..

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Clément Foucault self-assigned this 2019-03-04 17:06:56 +01:00

In #62030#632183, @nokipaike wrote:
@mano-wii Nice Strike man!

... in heavy scenes, now the gpu feels that it works more (the fan will turn faster to cool)

The change in the GPU work should not be significant.
It's possible, but it's probably not related.
However I realize that there are some areas to optimize.
Certainly these areas will be considered in future tasks.

> In #62030#632183, @nokipaike wrote: > @mano-wii Nice Strike man! > > ... in heavy scenes, now the gpu feels that it works more (the fan will turn faster to cool) > The change in the GPU work should not be significant. It's possible, but it's probably not related. However I realize that there are some areas to optimize. Certainly these areas will be considered in future tasks.
Author

the shaders now take a bit more to take shape the first time I set the scene in EEVEE mode, and even to load they put a pinch more ... I always talk about those heavy scenes ...

And I also noticed that the "vbo cache" now "saturates faster" ... and so if I make a switch between solid and eevee mode sometimes blender recalculate the shaders like the first time ...

the gpu no doubt works more intensely ... remember when I told you that "the fan worked at low rpm" while I was coloring that scene with the mechanic and the robots? ...

the shaders now take a bit more to take shape the first time I set the scene in EEVEE mode, and even to load they put a pinch more ... I always talk about those heavy scenes ... And I also noticed that the "vbo cache" now "saturates faster" ... and so if I make a switch between solid and eevee mode sometimes blender recalculate the shaders like the first time ... the gpu no doubt works more intensely ... remember when I told you that "the fan worked at low rpm" while I was coloring that scene with the mechanic and the robots? ...

@nokipaike I commited 798d2cadc3 which might be related to the perf improvement you got but i'm not certain. I also doubt @mano-wii 's commit made any different. But whatever, the result is here.

@nokipaike I commited 798d2cadc307 which might be related to the perf improvement you got but i'm not certain. I also doubt @mano-wii 's commit made any different. But whatever, the result is here.
Author

I also noticed something that is making me really very very happy ...
that once the "vbo" has recalculated ... the gui starts to become light and responsive ...
(I always speak in heavy scenes with eevee activated)
the opposite is that "this buffer on the gui" is downloaded and recalculated every time I set a new color or parameter in general ...
it is a pity that do so ...
but surely it is much better than before ..
and with some polish work ... you could get great results here.

I also noticed something that is making me really very very happy ... that once the "vbo" has recalculated ... the gui starts to become light and responsive ... (I always speak in heavy scenes with eevee activated) the opposite is that "this buffer on the gui" is downloaded and recalculated every time I set a new color or parameter in general ... it is a pity that do so ... but surely it is much better than before .. and with some polish work ... you could get great results here.
Author

I commited 798d2cadc3 which might be related to the perf improvement you got but i'm not certain.

@fclem I had not noticed this change you made today..
yes .. it could be also for this

> I commited 798d2cadc307 which might be related to the perf improvement you got but i'm not certain. @fclem I had not noticed this change you made today.. yes .. it could be also for this
Sign in to join this conversation.
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
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
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#62030
No description provided.