Bug 140515 - FILEOPEN Crash in: dbaui::OTasksWindow::onSelected(weld::TreeView &)
Summary: FILEOPEN Crash in: dbaui::OTasksWindow::onSelected(weld::TreeView &)
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-18 17:11 UTC by Lars Jødal
Modified: 2021-02-25 06:36 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["dbaui::OTasksWindow::onSelected(weld::TreeView &)"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Jødal 2021-02-18 17:11:12 UTC
This bug was filed from the crash reporting server and is br-e97c698f-f64f-435f-9abe-7297aca64e27.
=========================================
Activated experimental features in LO 7.1.0.3 and created (empty) database with embedded Firebird engine. Then opened a previously created database with HSQLDB engine. Upon opening the second database, LO crashed.
Comment 1 Xisco Faulí 2021-02-18 19:57:59 UTC
Hello Lars,
This might be fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=c08ec94ae04656e5178a704445080fe6887aac5a.

Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 2 Lars Jødal 2021-02-24 05:36:21 UTC
Hello Xisco,
I find that I cannot even reproduce in LO 7.1.0.3, i.e. the version in which I experienced the crash. Given that situation, I guess the report is of little value.

More generally, what is the value of a crash report sent in by LO? Is it only of value if followed by a bug report - that is reproducible?
Comment 3 Xisco Faulí 2021-02-24 08:32:38 UTC
(In reply to Lars Jødal from comment #2)
> Hello Xisco,
> I find that I cannot even reproduce in LO 7.1.0.3, i.e. the version in which
> I experienced the crash. Given that situation, I guess the report is of
> little value.
> 
> More generally, what is the value of a crash report sent in by LO? Is it
> only of value if followed by a bug report - that is reproducible?

See the comment in https://cgit.freedesktop.org/libreoffice/core/commit/?id=c08ec94ae04656e5178a704445080fe6887aac5a, maybe it gives you an idea on how to reproduce it
Comment 4 Lars Jødal 2021-02-25 06:36:17 UTC
(In reply to Xisco Faulí from comment #3)

> See the comment in
> https://cgit.freedesktop.org/libreoffice/core/commit/
> ?id=c08ec94ae04656e5178a704445080fe6887aac5a, maybe it gives you an idea on
> how to reproduce it

Now I get it. The comment ties the crash to opening a database by double-click in the file-open dialogue, and this way I was able to reproduce two crashes in three tests. This was LO 7.1.0.3:

Version: 7.1.0.3 (x64) / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: da-DK (da_DK); UI: da-DK
Calc: threaded

And yes, the issue seems to be fixed by the commit. Testing with LO 7.2.0.0.alpha0, I can no longer provoke a crash:

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: af64bc49d872d8a040d66387303def98eae5cd51
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: da-DK (da_DK); UI: da-DK
Calc: CL

So I am closing the bug. Thanks for the help.