Heavy lags over whole desktop environment #59996

Closed
opened 2018-12-31 01:42:26 +01:00 by Wojtek · 16 comments

System Information
Operating system: Linux Mint 18.3, MATE
Graphics card: can't actually find the exact model right now, it's Radeon 6xxxM

Blender Version
Broken: 2.80, 7c438e55366b2, 2018-12-28
Worked: sa far as I understand this gap to fill - 2.79 official releases worked as smoothly as the hardware allowed it to.

Blender and a very desktop environment lag heavily when B3D is in Object Mode

1 - I start with a basic scene with the cube
2 - i tweak its dimensions in edit mode, cut it with loop-cut a few times so the mesh is a bit more complex
3 - go back to object mode.

Actually Blender acts like it filled up whole RAM and then the system starts to use SWAP partition, while it's not SSD ;) but it's not it, there's still plenty of free RAM. Every 3d viewport click, every view turn, every tiny action with Blender is click-and-wait battle. Such action needs about 10-20s, then again a second of smoothness and another 10-20s of waiting.
I didn't find any solution on the Internet yet, so I might be one of the few with the issue.
Picture of the 'complex' mesh in the attachment.

Thank you in advance for your time and your hard work. Cheers!

simple-yet-troublesome-mesh.png

**System Information** Operating system: Linux Mint 18.3, MATE Graphics card: can't actually find the exact model right now, it's Radeon 6xxxM **Blender Version** Broken: 2.80, 7c438e55366b2, 2018-12-28 Worked: sa far as I understand this gap to fill - 2.79 official releases worked as smoothly as the hardware allowed it to. Blender and a very desktop environment lag heavily when B3D is in Object Mode 1 - I start with a basic scene with the cube 2 - i tweak its dimensions in edit mode, cut it with loop-cut a few times so the mesh is a bit more complex 3 - go back to object mode. Actually Blender acts like it filled up whole RAM and then the system starts to use SWAP partition, while it's not SSD ;) but it's not it, there's still plenty of free RAM. Every 3d viewport click, every view turn, every tiny action with Blender is click-and-wait battle. Such action needs about 10-20s, then again a second of smoothness and another 10-20s of waiting. I didn't find any solution on the Internet yet, so I might be one of the few with the issue. Picture of the 'complex' mesh in the attachment. Thank you in advance for your time and your hard work. Cheers! ![simple-yet-troublesome-mesh.png](https://archive.blender.org/developer/F6122797/simple-yet-troublesome-mesh.png)
Author

Added subscriber: @ototto

Added subscriber: @ototto

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Attach the output of --debug-gpu and you can also try to see if --debug-gpu-force-workarounds fixes it.

This is probably a GPU driver issue though if it freezes your whole computer. So I suggest you try to update your mesa drivers to the latest version too.

Attach the output of `--debug-gpu` and you can also try to see if `--debug-gpu-force-workarounds` fixes it. This is probably a GPU driver issue though if it freezes your whole computer. So I suggest you try to update your mesa drivers to the latest version too.

Added subscriber: @nokipaike

Added subscriber: @nokipaike

@ototto

do you also have problems like this?
https://developer.blender.org/T60001
I'm using the last mesa ppa by oibaf
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
the drivers in developing have improved .. for a while .. but with the recent builds of blender problems have emerged ..
I hope they solve

@ototto do you also have problems like this? https://developer.blender.org/T60001 I'm using the last mesa ppa by oibaf https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers the drivers in developing have improved .. for a while .. but with the recent builds of blender problems have emerged .. I hope they solve
Author

Thx guys, I really appreciate.

Drivers - checked, updated, upgraded. No difference though.

@nokipaike - nope, Eevee works like gold on such simple scenes, no gibberish like this on the videos from your thread.
@ZedDB - there's '--debug-gpu' output in the attachment. Sorry if it's too big, I'm not sure what part of it is the most interesting to you. Those are lines from the very command until I quit Blender after it's ceases to cooperate. The good news is that '-force-workorounds' suffix does the job on the mesh, so yay :)

Suddenly:
The very identical symptoms appear right after I make a bone chain 6-bones long. No less, no more (I didn't manage to create longer one ;)). Plus the mode (object, edit, pose) doesn't matter, Blender misbehaves in all three. There... I have no clue at all and the 'force-workarounds' suffix won't help anymore.
Another CLI output in another attachment. The fatal error at the end is 'xkill'-forced-quit, so you don't have to bother.
So... Hope it helps... and hope you guys help me ;)

cheers!
blender-debug-gpu-output.txt

BONES-blender-debug-gpu-output.txt

Thx guys, I really appreciate. Drivers - checked, updated, upgraded. No difference though. @nokipaike - nope, Eevee works like gold on such simple scenes, no gibberish like this on the videos from your thread. @ZedDB - there's '--debug-gpu' output in the attachment. Sorry if it's too big, I'm not sure what part of it is the most interesting to you. Those are lines from the very command until I quit Blender after it's ceases to cooperate. The good news is that '-force-workorounds' suffix does the job on the mesh, so yay :) Suddenly: The very identical symptoms appear right after I make a bone chain 6-bones long. No less, no more (I didn't manage to create longer one ;)). Plus the mode (object, edit, pose) doesn't matter, Blender misbehaves in all three. There... I have no clue at all and the 'force-workarounds' suffix won't help anymore. Another CLI output in another attachment. The fatal error at the end is 'xkill'-forced-quit, so you don't have to bother. So... Hope it helps... and hope you guys help me ;) cheers! [blender-debug-gpu-output.txt](https://archive.blender.org/developer/F6142936/blender-debug-gpu-output.txt) [BONES-blender-debug-gpu-output.txt](https://archive.blender.org/developer/F6143150/BONES-blender-debug-gpu-output.txt)
Clément Foucault was assigned by Sebastian Parborg 2019-01-01 23:35:54 +01:00

what it the output of glxinfo | grep -i opengl ?
I'm guessing this might be solved in newer mesa versions.

what it the output of `glxinfo | grep -i opengl` ? I'm guessing this might be solved in newer mesa versions.

@ototto
I thought it was the same generation of radeon hd as my gpu ..

instead I read better and your radeon is not a hd
@ototto I thought it was the same generation of radeon hd as my gpu .. ``` instead I read better and your radeon is not a hd
Author

@ZedDB
Took me a while :/

glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

So that's the output you've asked.
Sorry for the time of my reaction.

@ZedDB Took me a while :/ ``` glxinfo | grep -i opengl OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ``` So that's the output you've asked. Sorry for the time of my reaction.

Seems like you are using your built in GPU and not your Radeon gpu.

So I will suggest two things:

  1. Figure out how to switch to your dedicated GPU
  2. Update mesa version as the one you have is about half a year old. (So you might be missing some bug fixes for your GPU drivers [mesa])
Seems like you are using your built in GPU and not your Radeon gpu. So I will suggest two things: 1. Figure out how to switch to your dedicated GPU 2. Update mesa version as the one you have is about half a year old. (So you might be missing some bug fixes for your GPU drivers [mesa])

@ototto

DRI_PRIME=1 ./blender

if your system has 2 GPUs

@ototto ``` DRI_PRIME=1 ./blender ``` if your system has 2 GPUs
Author

Alright. I feel stupid now, but hey - the 2.79 worked just fine... :/ And as long as Cycles does not support this particular Radeon card, I simply didn't notice. Shame on me.
Maybe it's time to change my machine, simply enough.

Thank you, gentlemen :) Cheers!

Alright. I feel stupid now, but hey - the 2.79 worked just fine... :/ And as long as Cycles does not support this particular Radeon card, I simply didn't notice. Shame on me. Maybe it's time to change my machine, simply enough. Thank you, gentlemen :) Cheers!

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

I'll close this as resolved then (?)

I'll close this as resolved then (?)
Author

Yup, go ahead :) thanks again.

Yup, go ahead :) thanks again.

@ototto so...

do you also have problems like this?
https://developer.blender.org/T60001

@ototto so... > > do you also have problems like this? > https://developer.blender.org/T60001
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
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
3 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#59996
No description provided.