Red Hat Bugzilla – Bug 1286416
[abrt] soffice.bin killed in llvm::MachineFrameInfo::setObjectAlignment
Last modified: 2016-12-20 11:24:10 EST
Version-Release number of selected component:
crash_function: (anonymous namespace)::AutoRecovery::implts_registerDocument
runlevel: N 5
Thread no. 1 (10 frames)
#0 (anonymous namespace)::AutoRecovery::implts_registerDocument at /usr/src/debug/libreoffice-188.8.131.52/framework/source/services/autorecovery.cxx:2483
#1 (anonymous namespace)::AutoRecovery::implts_verifyCacheAgainstDesktopDocumentList at /usr/src/debug/libreoffice-184.108.40.206/framework/source/services/autorecovery.cxx:4152
#2 (anonymous namespace)::AutoRecovery::implts_prepareEmergencySave at /usr/src/debug/libreoffice-220.127.116.11/framework/source/services/autorecovery.cxx:3706
#3 (anonymous namespace)::AutoRecovery::implts_dispatch at /usr/src/debug/libreoffice-18.104.22.168/framework/source/services/autorecovery.cxx:1450
#4 (anonymous namespace)::AutoRecovery::dispatch at /usr/src/debug/libreoffice-22.214.171.124/framework/source/services/autorecovery.cxx:1394
#5 svx::DocRecovery::RecoveryCore::doEmergencySavePrepare at /usr/src/debug/libreoffice-126.96.36.199/svx/source/dialog/docrecovery.cxx:305
#6 svx::DocRecovery::SaveDialog::SaveDialog at /usr/src/debug/libreoffice-188.8.131.52/svx/source/dialog/docrecovery.cxx:645
#7 ScopedVclPtrInstance<svx::DocRecovery::SaveDialog>::ScopedVclPtrInstance<VclPtr<vcl::Window>&, svx::DocRecovery::RecoveryCore*&> at /usr/src/debug/libreoffice-184.108.40.206/include/vcl/vclptr.hxx:374
#8 (anonymous namespace)::RecoveryUI::impl_doEmergencySave at /usr/src/debug/libreoffice-220.127.116.11/svx/source/unodraw/recoveryui.cxx:248
#9 (anonymous namespace)::RecoveryUI::dispatchWithReturnValue at /usr/src/debug/libreoffice-18.104.22.168/svx/source/unodraw/recoveryui.cxx:168
Created attachment 1100133 [details]
Created attachment 1100134 [details]
Created attachment 1100135 [details]
Created attachment 1100136 [details]
Created attachment 1100137 [details]
Created attachment 1100138 [details]
Created attachment 1100139 [details]
Created attachment 1100140 [details]
Created attachment 1100141 [details]
Created attachment 1100142 [details]
Created attachment 1100143 [details]
Created attachment 1100144 [details]
Created attachment 1100145 [details]
The original crash is in llvm at:
> #16 <signal handler called>
> #17 0x00007efbc2c7ab7b in llvm::MachineFrameInfo::setObjectAlignment (Align=4, ObjectIdx=-1, this=0x56555c31f4f0) at /usr/src/debug/llvm-3.7.0.src/include/llvm/CodeGen/MachineFrameInfo.h:405
> #32 0x00007efbcd731c0b in radeon_llvm_compile (M=M@entry=0x56555bbaa060, binary=binary@entry=0x56555c471c60, gpu_family=<optimized out>, dump_ir=dump_ir@entry=false, dump_asm=dump_asm@entry=false, tm=tm@entry=0x56555b509570) at radeon_llvm_emit.c:190
> #33 0x00007efbcd697378 in si_compile_llvm (sscreen=sscreen@entry=0x56555ad12e70, shader=shader@entry=0x56555c471c30, tm=tm@entry=0x56555b509570, mod=0x56555bbaa060) at si_shader.c:3873
> #40 0x00007efbcd2432aa in vbo_draw_arrays (ctx=0x56555b43ebd0, mode=6, start=0, count=4, numInstances=1, baseInstance=0) at vbo/vbo_exec_array.c:645
> #41 0x00007efbf25a20c7 in OpenGLProgram::DrawTexture (this=this@entry=0x56555c425810, rTexture=...) at /usr/src/debug/libreoffice-22.214.171.124/vcl/opengl/program.cxx:302
(The subsequent crash of LibreOffice during the auto-recovery attempt run from the signal handler---which can never be completely reliable by design---will be addressed in libreoffice-126.96.36.199-9.fc23.)
libreoffice-188.8.131.52-10.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-8cdbd2bb12
libreoffice-184.108.40.206-10.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update libreoffice'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-8cdbd2bb12
libreoffice-220.127.116.11-10.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Fedora Update System from comment #15)
> libreoffice-18.104.22.168-10.fc23 has been submitted as an update to Fedora 23.
That fix was for the "subsequent crash of LibreOffice during the auto-recovery attempt run from the signal handler," not for the root cause.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.