Bug 99473 - assertion "SolarMutex not locked"
Summary: assertion "SolarMutex not locked"
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2.0.0.alpha0+
Hardware: All All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Crash-Assert
  Show dependency tree / graph
 
Reported: 2016-04-23 23:31 UTC by Terrence Enger
Modified: 2017-02-05 13:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
`make debugrun` (24.61 KB, text/plain)
2016-04-23 23:31 UTC, Terrence Enger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Terrence Enger 2016-04-23 23:31:11 UTC 
Created attachment 124592 [details]
`make debugrun`

Error message is around line 61, `backtrace full` around line 69.

The error message is (newllines added) ...
    soffice.bin:
        /home/terry/lo_hacking/git/libo6/vcl/source/app/dbggui.cxx:47:
        void ImplDbgTestSolarMutex(): Assertion
        `ImplGetSVData()->mpDefInst->CheckYieldMutex() && "SolarMutex
        not locked"' failed.


STR
---
(1) Run Calc from the command line.  Program presents Calc window
    "Untitled 1".
(2) In Calc window, type "<Ctrl>+F".  Program open find toolbar at
    bottom of the window.
(3) Type "a<Enter>".  No visible result.
(4) Type "<Esc>".  Program closes find toolbar.
(5) Type "<Alt>+E F".  Program crashes.  For comparison, "<Ctrl>+F" at
    this point simply opens the find toolbar again.

This observation is from commit 5892c6b, fetched 2016-04-23,
configured ...
    CC=ccache /usr/bin/gcc
    CXX=ccache /usr/bin/g++
    --enable-option-checking=fatal
    --enable-dbgutil
    --enable-debug
    --enable-crashdump
    --without-system-postgresql
    --without-myspell-dicts
    --with-extra-buildid
    --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
built and running on debian-wheezy.

I am setting bug status NEW.
Comment 1 Julien Nabet 2016-04-24 09:08:05 UTC 
On pc Debian x86-64 with master sources updated today, I could reproduce this too.
Comment 2 Aron Budea 2016-06-11 07:10:53 UTC 
Seems to be fixed now in beta2. Please retest.
Comment 3 Aron Budea 2016-06-11 07:15:13 UTC 
Oops, I forgot assertion only comes up in debug build, never mind then.
So I don't know about the current status, but I wonder if it can be fixed along the same lines as the steps described in bug 96365.
Comment 4 Julien Nabet 2016-06-11 07:48:38 UTC 
With master sources updated yesterday (fd8f328462fc20d9a3a03b5f8ceb78faedeaa602), I still reproduce this.
Comment 5 Aron Budea 2016-06-11 08:24:24 UTC 
Just checked in Windows, the assert pops up there as well.
Comment 6 Julien Nabet 2017-02-05 11:28:03 UTC 
Terrence/Aron: On pc Debian x86-64 with master sources updated today, I don't reproduce this.
Could you give it a new try?
Comment 7 Terrence Enger 2017-02-05 13:50:00 UTC 
Thank you, Julien, for the reminder.

The bug seems to be gone in master commit 9ba5eb22, pulled 2017-02-03,
configured ...
    CC=ccache /usr/bin/gcc
    CXX=ccache /usr/bin/g++
    --enable-option-checking=fatal
    --enable-dbgutil
    --enable-debug
    --without-system-postgresql
    --without-myspell-dicts
    --with-extra-buildid
    --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
    --without-package-format
built and running on debian-stretch.

I am setting status RESOLVED WORKSFORME.