Description of problem: Writer crashes on document opening. Version-Release number of selected component: libreoffice-core-4.2.5.2-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --writer --splash-pipe=5 crash_function: std::_Rb_tree<writerfilter::dmapper::PropertyIds, std::pair<writerfilter::dmapper::PropertyIds const, writerfilter::dmapper::PropValue>, std::_Select1st<std::pair<writerfilter::dmapper::PropertyIds const, writerfilter::dmapper::PropValue> >, std::less<writerfilter::dmapper::PropertyIds>, std::allocator<std::pair<writerfilter::dmapper::PropertyIds const, writerfilter::dmapper::PropValue> > >::find(writerfilter::dmapper::PropertyIds const&) const executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.15.3-200.fc20.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 std::_Rb_tree<writerfilter::dmapper::PropertyIds, std::pair<writerfilter::dmapper::PropertyIds const, writerfilter::dmapper::PropValue>, std::_Select1st<std::pair<writerfilter::dmapper::PropertyIds const, writerfilter::dmapper::PropValue> >, std::less<writerfilter::dmapper::PropertyIds>, std::allocator<std::pair<writerfilter::dmapper::PropertyIds const, writerfilter::dmapper::PropValue> > >::find(writerfilter::dmapper::PropertyIds const&) const at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #1 writerfilter::dmapper::DomainMapper::sprmWithProps(writerfilter::Sprm&, boost::shared_ptr<writerfilter::dmapper::PropertyMap>, writerfilter::dmapper::SprmType) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #2 writerfilter::dmapper::DomainMapper::lcl_sprm(writerfilter::Sprm&) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #3 writerfilter::rtftok::RTFReferenceProperties::resolve(writerfilter::Properties&) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #4 writerfilter::dmapper::DomainMapper::lcl_props(boost::shared_ptr<writerfilter::Reference<writerfilter::Properties> >) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #5 writerfilter::LoggedStream::props(boost::shared_ptr<writerfilter::Reference<writerfilter::Properties> >) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #6 writerfilter::rtftok::RTFDocumentImpl::checkNeedPap() at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #7 writerfilter::rtftok::RTFDocumentImpl::text(rtl::OUString&) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #8 writerfilter::rtftok::RTFDocumentImpl::resolveChars(char) at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so #9 writerfilter::rtftok::RTFTokenizer::resolveParse() at /usr/lib64/libreoffice/program/../program/libwriterfilterlo.so
Created attachment 917265 [details] File: backtrace
Created attachment 917266 [details] File: cgroup
Created attachment 917267 [details] File: core_backtrace
Created attachment 917268 [details] File: dso_list
Created attachment 917269 [details] File: environ
Created attachment 917270 [details] File: exploitable
Created attachment 917271 [details] File: limits
Created attachment 917272 [details] File: maps
Created attachment 917273 [details] File: open_fds
Created attachment 917274 [details] File: proc_pid_status
Created attachment 917275 [details] File: var_log_messages
Could you attach the document here?
That is a commercial document. It's just a system overview witrhout details, but still shouldn't be visible to the whole world. Is it possible to attach the document so that only assignee can use it for debugging and no one else?
If you mark the attachment as private, it will only be visible by people who have access to the bug: the reporter, the assignee, the QA contact and everyone in CC list. If that is still too much for you, you can mail the document to one of us.
(In reply to David Tardon from comment #14) > ... you can mail the document to one of us. For the record: I sent the document to your e-mail address, hopefully it reached the destination and you can continue debugging.
Does crash with 4.2.5.2, but not with 4.2.6.2.