Hide Forgot
Description of problem: @wayland again? Version-Release number of selected component: webkitgtk4-2.14.1-1.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 44 crash_function: llvm::TargetPassConfig::addMachinePasses executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess global_pid: 27879 kernel: 4.9.0-0.rc1.git0.2.fc26.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 llvm::TargetPassConfig::addMachinePasses at /usr/src/debug/llvm-3.8.0.src/lib/CodeGen/Passes.cpp:523 #1 addPassesToGenerateCode at /usr/src/debug/llvm-3.8.0.src/lib/CodeGen/LLVMTargetMachine.cpp:138 #2 llvm::LLVMTargetMachine::addPassesToEmitFile at /usr/src/debug/llvm-3.8.0.src/lib/CodeGen/LLVMTargetMachine.cpp:152 #3 LLVMTargetMachineEmit at /usr/src/debug/llvm-3.8.0.src/lib/Target/TargetMachineC.cpp:210 #4 LLVMTargetMachineEmitToMemoryBuffer at /usr/src/debug/llvm-3.8.0.src/lib/Target/TargetMachineC.cpp:240 #5 radeon_llvm_compile at radeon_llvm_emit.c:235 #6 si_compile_llvm at si_shader.c:6166 #7 si_compile_tgsi_shader at si_shader.c:6561 #8 si_create_shader_selector at si_state_shaders.c:1195 #9 ureg_create_shader at tgsi/tgsi_ureg.c:2031
Created attachment 1212455 [details] File: backtrace
Created attachment 1212456 [details] File: cgroup
Created attachment 1212457 [details] File: core_backtrace
Created attachment 1212458 [details] File: dso_list
Created attachment 1212459 [details] File: environ
Created attachment 1212460 [details] File: exploitable
Created attachment 1212461 [details] File: limits
Created attachment 1212462 [details] File: maps
Created attachment 1212463 [details] File: mountinfo
Created attachment 1212464 [details] File: namespaces
Created attachment 1212465 [details] File: open_fds
Created attachment 1212466 [details] File: proc_pid_status
Created attachment 1212467 [details] File: var_log_messages
[50936.051011] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* ttm_eu_reserve_buffers failed. [54029.096870] si_shader:2[23149]: segfault at 10 ip 00007f5a4de0cc7b sp 00007f5a4c239860 error 4 in libLLVM-3.9.so[7f5a4d475000+269a000] [54068.487732] WebKitWebProces[23769]: segfault at 10 ip 00007f9c98704c7b sp 00007f9c9611f300 error 4 in libLLVM-3.9.so[7f9c97d6d000+269a000] [54068.712751] si_shader:1[23728]: segfault at 10 ip 00007f46693acc7b sp 00007f46637f5860 error 4 in libLLVM-3.9.so[7f4668a15000+269a000]
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.