3.4, 3.5 mouse cursor randomly freezes for 0.5 to 2 seconds #107513

Closed
opened 2023-05-01 20:44:23 +02:00 by shannon zachow · 4 comments

System Information
Operating system: Linux / Manjaro
Graphics card: RTX2060

Blender Version
Broken: 3.4, 3.5
Worked: 3.3

Short description of error

blender hangs (mouse-cursor unresponsive) for 0.5 to 2 seconds, at irregular interval of every 30sec to 2min. (Not a full crash, control eventually returns)

Exact steps for others to reproduce the error

The only commonality to events is blender cursor update. Happens under all the following conditions:

  • mouse or pen-tablet
  • (cmd-line) launch normal, or launch with flag --factory-startup
  • just transforming ViewPort in Object-mode, or while Edit-mode on mesh or curve, or Sculpt-mode, or Weight-painting, or editing Armatures.
  • can be any ViewPort display-mode.
  • mouse can be in any part of the blender-window.
  • even happens with cmd-line animation player: $ blender -a
  • only happens in blender 3.4, 3.5. I can run 3.3 (3.3.3) right now with zero problems. Every other mouse-intensive "drawing/painting" program on my computer does not have this problem.

This started when v3.4 came out. I searched through bugs, and the only suggestion I found was to try 3.5-beta. Problem continued in 3.5-beta, and continues in Released Version of 3.5. It's like writing with a ball-point pen that only produces a line 98% of time... by the time you realize it's stopped working, your hand has moved 1-3" inches on screen, and stroke is ruined. Or like driving a car, where the steering wheel only listens to you 98% of time. :(

I did not file a bug-report before, because there is no way to describe "Steps to reproduce error". I'm filing now to provide feedback to developers, and maybe they can spot something in system-info.txt.

Thank you for blender.

**System Information** Operating system: Linux / Manjaro Graphics card: RTX2060 **Blender Version** Broken: 3.4, 3.5 Worked: 3.3 **Short description of error** blender hangs (mouse-cursor unresponsive) for 0.5 to 2 seconds, at irregular interval of every 30sec to 2min. (Not a full crash, control eventually returns) **Exact steps for others to reproduce the error** The only commonality to events is blender cursor update. Happens under all the following conditions: + mouse or pen-tablet + (cmd-line) launch normal, or launch with flag --factory-startup + just transforming ViewPort in Object-mode, or while Edit-mode on mesh or curve, or Sculpt-mode, or Weight-painting, or editing Armatures. + can be any ViewPort display-mode. + mouse can be in any part of the blender-window. + even happens with cmd-line animation player: $ blender -a <video>.mp4 + only happens in blender 3.4, 3.5. I can run 3.3 (3.3.3) right now with zero problems. Every other mouse-intensive "drawing/painting" program on my computer does not have this problem. This started when v3.4 came out. I searched through bugs, and the only suggestion I found was to try 3.5-beta. Problem continued in 3.5-beta, and continues in Released Version of 3.5. It's like writing with a ball-point pen that only produces a line 98% of time... by the time you realize it's stopped working, your hand has moved 1-3" inches on screen, and stroke is ruined. Or like driving a car, where the steering wheel only listens to you 98% of time. :( I did not file a bug-report before, because there is no way to describe "Steps to reproduce error". I'm filing now to provide feedback to developers, and maybe they can spot something in system-info.txt. Thank you for blender.
shannon zachow added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-05-01 20:44:24 +02:00
YimingWu changed title from blender 3.4, 3.5 hangs freezes unresponsive to 3.4, 3.5 mouse cursor randomly freezes for 0.5 to 2 seconds 2023-05-02 08:20:17 +02:00
Member

That sounds kinda weird. Cursor freeze seems to be your GPU constantly running some task.

Could you try blender -d --debug-all and try to see if there are any output in the terminal during freezing and also log files?

Another way to potentially mitigate the problem is to update/downgrade your nvidia driver, try use proprietary driver.

Thanks!

That sounds kinda weird. Cursor freeze seems to be your GPU constantly running some task. Could you try `blender -d --debug-all` and try to see if there are any output in the terminal during freezing and also log files? Another way to potentially mitigate the problem is to update/downgrade your nvidia driver, try use proprietary driver. Thanks!
YimingWu added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-05-02 08:25:24 +02:00

I had the same thing happen when I had "Node count" add-on enabled.
May want to try disabling addons to see if it goes away.

I had the same thing happen when I had "Node count" add-on enabled. May want to try disabling addons to see if it goes away.
Author

go ahead an close this bug report. I'll keep testing, but assume it is something at my end (drivers?) for now.

To Mike: I had tried with --factory-startup and still got the problem. I thought --factory-startup disabled all the addons. ?

To YimingWu: I tried with -d --debug-all as you requested. I managed to get the problem, and then looked at the terminal debug messages. A lot of normal wm reports before, during, and after the event... but nothing that looked like blender was at fault.

re: drivers:
I've taken a deep dive into the drivers on my system. I'm using (linux) Manjaro/Arch's PRIME-RUN prefix to force my hybrid laptop (has integrated intel GPU + discrete Nvidia GPU) to run blender with only the Nvidia GPU. It confuses me exactly which drivers are in operation at which time, but I BELIEVE that it is running version 530 of Nvidia's proprietary driver.
(note that there is a LOT of chatter online about people wanting to downgrade their Nvidia driver, so apparently all is not well there.)

re: pen-tablet:
all these warn me to only have 1 driver running the tablet. I had removed previous driver & installed new when I last upgraded my pen-tablet. Somewhere along the line, Manjaro went from having the "digimend" driver being out-of-tree in the AUR (ie; not part of the normal distribution), then when I installed a proprietary driver, Manjaro changed and put the "digimend" driver (for all non-wacom pen-tablets) into the main distribution, and installed it without LOUDLY telling me during a normal system upgrade. So I had 2 drivers. (grumble). I removed one of them.

as I kept poking at drivers, my system got pretty unstable, but then yesterday, there was an unscheduled system update to "system.d" (which is pretty key to linux), and I haven't seen the hiccup since then.

I have my fingers crossed, and will keep researching. I did manage to run blender 3.5 tonight for nearly 2 hours without the hiccup/hanging issue.

Thank you all for your input and help. Thank you for blender!

go ahead an close this bug report. I'll keep testing, but assume it is something at my end (drivers?) for now. To Mike: I had tried with --factory-startup and still got the problem. I thought --factory-startup disabled all the addons. ? To YimingWu: I tried with -d --debug-all as you requested. I managed to get the problem, and then looked at the terminal debug messages. A lot of normal wm reports before, during, and after the event... but nothing that looked like blender was at fault. re: drivers: I've taken a deep dive into the drivers on my system. I'm using (linux) Manjaro/Arch's PRIME-RUN prefix to force my hybrid laptop (has integrated intel GPU + discrete Nvidia GPU) to run blender with only the Nvidia GPU. It confuses me exactly which drivers are in operation at which time, but I BELIEVE that it is running version 530 of Nvidia's proprietary driver. (note that there is a LOT of chatter online about people wanting to downgrade their Nvidia driver, so apparently all is not well there.) re: pen-tablet: all these warn me to only have 1 driver running the tablet. I had removed previous driver & installed new when I last upgraded my pen-tablet. Somewhere along the line, Manjaro went from having the "digimend" driver being out-of-tree in the AUR (ie; not part of the normal distribution), then when I installed a proprietary driver, Manjaro changed and put the "digimend" driver (for all non-wacom pen-tablets) into the main distribution, and installed it without LOUDLY telling me during a normal system upgrade. So I had 2 drivers. (*grumble*). I removed one of them. as I kept poking at drivers, my system got pretty unstable, but then yesterday, there was an unscheduled system update to "system.d" (which is pretty key to linux), and I haven't seen the hiccup since then. I have my fingers crossed, and will keep researching. I did manage to run blender 3.5 tonight for nearly 2 hours without the hiccup/hanging issue. Thank you all for your input and help. Thank you for blender!
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-05-04 09:00:09 +02:00
Member

as I kept poking at drivers, my system got pretty unstable, but then yesterday, there was an unscheduled system update to "system.d" (which is pretty key to linux), and I haven't seen the hiccup since then.

I used to have my ubuntu update the kernel automatically and sometimes it broke the nvidia driver. maybe this is also that kind of weird issues.

> as I kept poking at drivers, my system got pretty unstable, but then yesterday, there was an unscheduled system update to "system.d" (which is pretty key to linux), and I haven't seen the hiccup since then. I used to have my ubuntu update the kernel automatically and sometimes it broke the nvidia driver. maybe this is also that kind of weird issues.
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#107513
No description provided.