Version-Release number of selected component: blender-1:3.1.0-7.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-blender-3494.scope cmdline: blender crash_function: _iris_batch_flush dso_list: /usr/bin/blender blender-1:3.1.0-7.fc35.x86_64 (Fedora Project) 1647978666 executable: /usr/bin/blender journald_cursor: s=09c17e512b614817b7d0f2c3f6b6b7a5;i=d2dff;b=abf58553e3b44bbeb0367ceb6eb0b74c;m=3af4d72e;t=5dae4ddffdf7f;x=5402c295caa599e kernel: 5.15.6-200.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1868182 [details] File: backtrace
Created attachment 1868183 [details] File: core_backtrace
Created attachment 1868184 [details] File: cpuinfo
Created attachment 1868185 [details] File: environ
Created attachment 1868186 [details] File: limits
Created attachment 1868187 [details] File: maps
Created attachment 1868188 [details] File: mountinfo
Created attachment 1868189 [details] File: open_fds
Created attachment 1868190 [details] File: proc_pid_status
Created attachment 1868191 [details] File: var_log_messages
I can’t find any existing reports similar to this in the upstream bug tracker at https://developer.blender.org/maniphest/. It looks like the SIGABRT was generated in code that specific to Intel Iris graphics, so that hardware is probably needed to reproduce this. If you can consistently reproduce the bug, please consider describing how to do so. Also, please consider reporting upstream (https://wiki.blender.org/wiki/Process/Bug_Reports) and linking the upstream report here. Thanks!
Actually, since _iris_batch_flush and all the other frames related to “../src/gallium/auxiliary” are in the iris driver rather than in Blender source, this might really be a mesa bug. See also bug 2072025.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.