Blender "crashes" unexpectedly: no error message

[Darkyyo]

In Blender, within the Masking tab of the VFX section, when I am in the process of adjusting the handles of a newly created mask to rotoscope a video, Blender constantly and randomly just freezes and "crashes"/closes itself, leaving this in the terminal:

Code: Select all

zsh: IOT instruction  blender-3.4

That's it, even after having started the program with:

Code: Select all

blender-3.4 --factory-startup --debug-all

I'm running version "3.4.1:3.4"; the issue was also apparent when using "3.3.2:3.3" and the stable "2.93.13:2.93". I know this isn't the best place to get help with Blender; however, before going to Stack Exchange, I just wanted to confirm: Could my kernel/USE flags setup possibly be causing any of this? Here are those:

Code: Select all

[ebuild   R   ~] media-gfx/blender-3.4.1:3.4::gentoo  USE="X bullet cycles embree ffmpeg fftw gmp nanovdb nls oidn openexr openimageio openmp pdf pugixml pulseaudio tbb tiff -alembic -collada -color-management -cuda -dds -debug -doc -fluid -jack -jemalloc -jpeg2k -man -ndof -openal -opensubdiv -openvdb -optix -osl -potrace -sdl -sndfile -test -valgrind -wayland" PYTHON_SINGLE_TARGET="python3_10"

.config

[_integralpanther_]

If you haven't found any solution in the blender forum you need to supply at least a backtrace or any kind of debug information.

The best would be to recompile at leasst blender (and probably more dependencies) with debug info (https://wiki.gentoo.org/wiki/Debugging) and let blender run inside gdb until the crash occurs. Then post us the stacktrace info you get there. The crash could happen in one of the dependencies of blender. Then its a different issue.

[wjb]

The "zsh: IOT instruction ..." message looks like its the shell (zsh?) helpfully pointing out that Blender has been terminated in a bad way, and isn't telling you anything about why this happened. That info would be buried somewhere in the reams of stuff generated by "--debug-all". Possibly try with "--debug" which is a lot quieter.

Just a thought ... the zsh shell reacts to a SIGABRT as above, and an abort() call raises a SIGABRT - you'd expect someone to log the reason for doing that.

A relatively quick way to figure out if the problem is the built software or the PC hardware config is to download the pre-built binary from the Blender site, unpack it in a user directory and run it from there. If this has the same problem, it's either the PC h/w (or a Blender bug). If it works ok, it suggests the problem is with the built software.

[Darkyyo]

I've tried wjb's suggestion. The issue was also present when using a pre-compiled Blender binary, so it's very probably a lack of decent hardware on my end. I checked my GPU RAM by doing:

Code: Select all

lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) (prog-if 00 [VGA controller])
        DeviceName:  Onboard IGD
        Subsystem: Dell Skylake GT2 [HD Graphics 520]
        Flags: bus master, fast devsel, latency 0, IRQ 122
        Memory at de000000 (64-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: i915

Unless I checked/interpreted incorrectly, it may all come down to the fact that it doesn't meet Blender's minimum requirements.

[shadowless]

For Intel GPUs, it states 'Haswell architecture and newer', which you do have..

Just curious... what do you have set for the VIDEO_CARDS variable in /etc/portage/make.conf ?

[Darkyyo]

Code: Select all

VIDEO_CARDS="intel"

[wjb]

I'm not crazy about the intel graphics other than for general home/office use ...

Two years ago, I was trying to use the integrated intel graphics (i7 10k plus 32GB) with Blender and was not having a good time. I had random lockups with physics and animations, and these also froze the desktop so it was very difficult. I tried with an nvidia 720 from an old PC and had no lockups doing the same kind of things. I ended up buying an nvidia 1030 to keep me going till the prices for modern cards returned to sane levels. It felt like the 1030 was about the same responsiveness as the integrated graphics, plus it was absolutely stable for Blender.

[szatox]

I don't know how wide-spread it it is, but I remember I've ran into some weird interaction between intel driver and blender. I think it's a bug in the driver actually. Either way, the bottom line was: it doesn't work and there is nothing you can do right now.


In my case the whole GUI would just freeze semi-randomly and had to be reset. I think I could still access text terminal, but there was no way to recover even the user session.