Page MenuHome

Prefetch with Proxy 50% causes Segmentation fault (core dumped)
Closed, ArchivedPublic


System Information
OS: Manjaro Linux x86_64
Host: 81NC Lenovo IdeaPad S340-15API
Kernel: 5.8.18-1-MANJARO
DE: GNOME 3.38.2
WM: Mutter
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8) @ 2.100GHz
GPU: AMD Radeon(TM) Vega 8 Graphics (RAVEN, DRM 3.38.0, 5.8.18-1-MANJARO, LLVM 11.0.0)
Memory: 7289MiB / 18006MiB

Blender Version
Broken: Blender 2.91.0

Short description of error
I am editing a few photos into a 1920x1080 video with the Video Editing Layout and when Prefetchs Frames at Proxy size 50% it crashes at about 400 frames (varies a lot 120 - 700) with a Segmentation fault (core dumped).
The whole clip is about 799 frames.

Terminal output:

[harry@harry-s340 Videos]$ blender skid-photos.blend
Read prefs: /home/harry/.config/blender/2.91/config/userpref.blend
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
Read blend: /home/harry/Videos/skid-photos.blend
Writing: /tmp/skid-photos.crash.txt
Segmentation fault (core dumped)
[harry@harry-s340 Videos]$


Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
I do not have permission to upload the photos but they all were 4032x3024 JPEG and each were 100 frames.

Blender file:

Event Timeline

Harry S (Haz_001) renamed this task from Prefetch with Proxy 50% causes to Prefetch with Proxy 50% causes Segmentation fault (core dumped).Jan 2 2021, 6:02 AM
Harry S (Haz_001) created this task.
Robert Guetzkow (rjg) changed the task status from Needs Triage to Needs Information from User.EditedJan 2 2021, 11:10 AM

I couldn't reproduce a crash in 2.91 or 2.92. Just to rule it out as potential cause, have you checked if you're running out of memory? This could potentially lead to a memory allocation failing. Dereferencing the resulting NULL pointer would lead to a crash.

Robert Guetzkow (rjg) closed this task as Archived.Jan 9 2021, 2:39 PM

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.