On Thu, 2019-11-21 at 15:54 +0100, Michael Stahl wrote:
On 21.11.19 15:17, Crashtest VM wrote:
New crashtest update available at
http://dev-builds.libreoffice.org/crashtest/299a13e8f7307b38ac10ad351273e2559e21ab16/
we have run some business intelligence AI algorithms via mapreduce
on
the clouds to classify the crashes:
for f in *; do grep -A2 __assert_fail $f | tail -n 1; done | cut -f
4 -d ' ' | sort | uniq -c
1 (anonymous
1
com::sun::star::uno::Reference<com::sun::star::frame::XModel>::operat
or->
176 DocxAttributeOutput::CharColor
36 sax_fastparser::FastSaxSerializer::writeFastAttributeList
I think both of these are since the same commit of
1d81d52b5da45f26e9d3adeb3b279eb9a488b94f I think I'll revert that with
https://gerrit.libreoffice.org/#/c/83406/ to get the noise level down
1 SwIndexReg::~SwIndexReg
5 SwSubFont::GetTextSize_
this one is my fault ^
14 writerfilter::dmapper::DomainMapper_Impl::PushFootOrEndnote
I believe ^this^ one is since
commit a991ad93dcd6807d0eacd11a50c2ae43a2cfb882
Author: Jan-Marek Glogowski <jan-marek.glogowski@extern.cib.de>
Date: Tue Oct 22 12:24:43 2019 +0200
tdf#121441 improve DOCX footnote import
caolanm->jmux: Import of e.g. tdf103063-1.docx is an example of these
14, any ideas on that assert ?
1 writerfilter::dmapper::DomainMapper_Impl::RemoveTopRedline
for f in *; do grep -A1 "signal [0-57-9]" $f | tail -n 1; done |
cut -f 5 -d ' ' | sort | uniq -c
6 chart::WrappedProperty::getPropertyState
1 (this=0x5cbe690,
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.