I am currently having issues with using Blender on my desktop computer where Blender just locks up/stops responding randomly while I manipulate positions of objects or node graphs. Blender never unlocks and there does not seem to be a consistent cause for this issue. All other programs run fine while Blender is locked up. My computer is not locked due to memory, CPU, nor GPU usage.

Please, if anyone can provide any information on this, I would greatly appreciate it!

Computer details:

Blender version: 3.6.1, only non-default add-on is MolecularNodes v2.7.4

OS: Pop!_OS 22.04

GPUs: GeForce GTX 1080, GeForce GTX Titan X (both pretty old, but still running strong with other visualization softwares)

GPU Driver: 535.104.05

CUDA Version: 12.2

CPU: Intel® Core™ i7-7700K CPU @ 4.20GHz

RAM: 32 GB

Edit: just noticed that Blender is still using 100% CPU (one thread of 8) even after being locked for 15+ minutes now.

Edit 2: Added Blender version and add-on details (duh).

Edit 3: This is not arising due to loading corrupt blender files. I just started a fresh run, recreating the desired blender process for the visualizations that I am interested in, and the program still locked up.

  • mvirts@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Can you try disabling accelerated rendering? Like turn off cuda in the preferences… I think there’s also opencl or something, it’s been a while…

    Really sounds like a blender bug. Feel up for attaching gdb to it and maybe getting a function name?

  • canadaduaneOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Here’s how I would investigate this:

    1. Try disabling MolecularNodes (and any other add-on) just to be sure it isn’t the culprit
    2. The CPU usage seems like an important clue. When you say “My computer is not locked due to memory, CPU, nor GPU usage”, how does this relate to “just noticed that Blender is still using 100% CPU”? Any chance it is trying to render via CPU instead of GPU?
    3. Check the journalctl logs on the command-line, i.e. in the Terminal app, type journalctl | grep -i blender (the symbol between journalctl and grep is a pipe aka vertical bar) I’d be looking for things like crashed processes, warnings, or errors, especially around the time of the freeze.