Bug 100147 - MacOS only textbox-wps-only fails
Summary: MacOS only textbox-wps-only fails
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.0.0.alpha0+
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-30 19:17 UTC by Julien Nabet
Modified: 2016-11-17 19:41 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
console bt logs (11.74 KB, text/plain)
2016-05-30 19:17 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Nabet 2016-05-30 19:17:00 UTC
Created attachment 125398 [details]
console bt logs

On Mac OS X 10.11.5, with master sources updated yesterday + lode use + enable-dbgutil, the build fails.
It's been like this since several months and it's a bit the following of  tdf#95294 but with a newer MacOs version.

Apple LLVM version 7.3.0 (clang-703.0.31)
Target: x86_64-apple-darwin15.5.0
Thread model: posix

java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)

Valgrind doesn't work in MacOs 10.11 and lldb only gives some assembly.
Comment 1 raal 2016-05-31 04:44:40 UTC
Hello Julien, please see
https://wiki.documentfoundation.org/QA/BugReport#Not_all_bugs_go_to_Bugzilla
It's this case  Building LibreOffice ->Development/Mailing List?
Comment 3 Alex Thurgood 2016-06-03 11:31:06 UTC
Hi Julien

--enable-dbgutil has been broken for me for some months now 

I only build with build-nocheck, as it is the only way I can get LO to build successfully on Mac OSX 10.11.5 / XCode 7.3
Comment 4 Julien Nabet 2016-06-03 12:07:57 UTC
(In reply to Alex Thurgood from comment #3)
> Hi Julien
> 
> --enable-dbgutil has been broken for me for some months now 
> 
> I only build with build-nocheck, as it is the only way I can get LO to build
> successfully on Mac OSX 10.11.5 / XCode 7.3

Do you have this exact same problem or some other problem with enable-dbgutil?
It could be great to tackle this one. Indeed I suppose some MacOs bugs only would need maximum of information to debug.
Comment 5 Julien Nabet 2016-06-07 20:13:52 UTC
I noticed this trace happens lots of lines after this:
tdf99140.docx:
645
warn:legacy.osl:95797:1:include/cppuhelper/interfacecontainer.h:479: object is disposed
warn:legacy.osl:95797:1:include/cppuhelper/interfacecontainer.h:479: object is disposed
/Users/marylinevogel/lo/lode/dev/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:1864: Assertion
Test name: textboxWpsOnly::Import
equality assertion failed
- Expected: 2805
- Actual  : 21779

Failures !!!
Run: 217   Failure total: 1   Failures: 1   Errors: 0
warn:tools.debug:95797:1:tools/source/debug/debug.cxx:72: no DbgTestSolarMutex function set
warn:fwk:95797:1:framework/source/services/desktop.cxx:1027: Desktop disposed before terminating it
warn:tools.debug:95797:1:tools/source/debug/debug.cxx:72: no DbgTestSolarMutex function set

2016-06-07 21:57:15.007 cppunittester[95797:1631267] *** -[NSAutoreleasePool release]: This pool has already been released, do not drain it (double release).
warn:tools.debug:95797:1:tools/source/debug/debug.cxx:72: no DbgTestSolarMutex function set
warn:legacy.osl:95797:1:unotools/source/config/configmgr.cxx:168: OSL_ASSERT: items_.empty()

I searched about "textbox-wps-only" and found this:
// FIXME: The assert below fails wildly on a Retina display
http://opengrok.libreoffice.org/xref/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx#1845

But I've got an Imac12.1 (i5 21.5 inches, mid 2011) so it doesn't seem Retina.
Comment 6 Alex Thurgood 2016-06-08 16:44:51 UTC
Hi Julien, my first failure in dbgutil enabled build is with libreportlo.dylib in a cppunit test. As I can't get past that one without switching off the checks, I don't know if others would follow.

FWIW, I'm not building on a retina capable Mac either, I'm using a Mac mini (server) that is now 5 years old.
Comment 7 Julien Nabet 2016-06-16 19:20:36 UTC
I renamed the title because it seems the original doesn't happen.
Since I was the only one to have this, I thought I could recycle this bugtracker.
If I'm wrong, don't hesitate to tell me and I'll open a new bugtracker.
Comment 8 Julien Nabet 2016-06-18 10:55:15 UTC
Alex: just for information, with master sources updated yesterday, I put a return in textbox-wps-only to see if it was the only problem for building and it was the case!
I used quite a minimum autogen.input:
disable-firebird
--enable-werror
--enable-dbgutil
--enable-debug
--disable-firebird-sdbc
with lode (see https://wiki.documentfoundation.org/Development/lode)
I use last 10.11 with last updates.

At least I could launch LO apps!
Comment 9 Julien Nabet 2016-06-18 10:57:01 UTC
Tor: noticing https://cgit.freedesktop.org/libreoffice/core/commit/?id=ce4412b52f50957117af5c472ca16974a51b2936, thought you might have some idea why textboxWpsOnly fails on my desktop (see https://bugs.documentfoundation.org/show_bug.cgi?id=100147#c5).
If it's not the case, any idea who may help here?
Comment 10 Buovjaga 2016-10-13 09:46:27 UTC
I poked Tor on IRC and he didn't have an idea about the issue. Some Writer expert can help.
Comment 11 steve 2016-10-23 20:10:32 UTC
Setting to NEEDINFO → @Julien, could you retest this? Is the bug persisting? Are you still on 10.11? Maybe 10.12 changes something for the better or worse and LO may behave differently by now.

Would be nice, to have this re-checked.
Comment 12 Julien Nabet 2016-10-23 20:26:04 UTC
It seems migrating to 10.12 isn't a good idea for the moment. :-)
However, I'll give a new try with the bypass I usually for this test.
Comment 13 Julien Nabet 2016-10-24 05:55:57 UTC
With master sources updated yesterday (2e137e4696e8278c3d56ba8a49a8b255534bd048), I still reproduce the problem:
/Users/XXX/lo/lode/dev/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:715: Assertion
Test name: textboxWpsOnly::Import
equality assertion failed
- Expected: 2805
- Actual  : 21779

Failures !!!
Run: 62   Failure total: 1   Failures: 1   Errors: 0
Comment 14 Alex Thurgood 2016-10-24 11:18:06 UTC
Hi Julien,

I think you should set this to new anyway. I don't encounter that particular problem with my own builds, but we're not using exactly the same build switches.
Comment 15 Alex Thurgood 2016-10-24 11:20:49 UTC
@Julien : fwiw, I can build pretty much just fine so far on Sierra, but I'm not using the lode setup
Comment 16 Julien Nabet 2016-10-24 12:08:34 UTC
Alex: no pb to let this unconfirmed, waiting for it's confirmed by someone else.
My only concern is to not close this one as WFM, INVALID or something.
I'm ready to test any suggested patch or add some logs to investigate.
(I'm also ready to let any LO dev/qa to access my MacOs (when I'm here! :-)) via Teamviewer.)
Comment 17 Julien Nabet 2016-11-01 12:17:30 UTC
I've upgraded to 10.12.1 + updated my local repo (04055cd8d9fcff67513cfd7de0872cb48bc82967) but now I got another fail (which happens before the one of the tracker):
tdf99140.docx:
921
testTdf99140::Import_Export_Import finished in: 973ms
/Users/XXX/lo/lode/dev/core/sw/qa/extras/ooxmlexport/ooxmlexport8.cxx:1278: Assertion
Test name: testMceNested::Import
assertion failed
- Expression: 6985 <= getProperty<sal_Int32>(xShape, "VertOrientPosition")

/Users/XXX/lo/lode/dev/core/sw/qa/extras/ooxmlexport/ooxmlexport8.cxx:1278: Assertion
Test name: testMceNested::Import_Export_Import
assertion failed
- Expression: 6985 <= getProperty<sal_Int32>(xShape, "VertOrientPosition")

Failures !!!
Run: 314   Failure total: 2   Failures: 2   Errors: 0
Comment 18 Julien Nabet 2016-11-01 13:18:22 UTC
I commented the precedent test to see if situation was better for this bug.
Badfully, it's still ko:
/Users/marylinevogel/lo/lode/dev/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:715: Assertion
Test name: textboxWpsOnly::Import
equality assertion failed
- Expected: 2805
- Actual  : 17658

Failures !!!
Run: 62   Failure total: 1   Failures: 1   Errors: 0

(notice that actual value changed)
Comment 19 Julien Nabet 2016-11-17 19:41:15 UTC
With master sources updated today, I don't reproduce this!!

I tried 2 times, each time with a "git pull -r && make clean && make"
At last! :-)