Bug 133309 - Crash in: com::sun::star::uno::operator<<=<com::sun::star::uno::Reference<com::sun::star::beans::XPropertySet> >(com::sun::star::uno::Any &,com::sun::star::uno::Reference<com::sun::star::beans::XPropertySet> const &)
Summary: Crash in: com::sun::star::uno::operator<<=<com::sun::star::uno::Reference<com...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: possibleRegression
Depends on:
Blocks: Crash
  Show dependency tree / graph
 
Reported: 2020-05-23 14:08 UTC by altmeier@pca-gmbh.com
Modified: 2021-11-19 05:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["com::sun::star::uno::operator<<=<com::sun::star::uno::Reference<com::sun::star::beans::XPropertySet> >(com::sun::star::uno::Any &,com::sun::star::uno::Reference<com::sun::star::beans::XPropertySet> const &)"]

Attachments
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 altmeier@pca-gmbh.com 2020-05-23 14:08:20 UTC 
This bug was filed from the crash reporting server and is br-2c10e3c3-6097-45e6-be34-4cce95082dce.
=========================================
The document crashes down when clicking into a Tebellen-Steuerelement.
This happens from Version 6 and I have now the 7.0.0.0, which also crashes. Not everytime, only sometimes.
Comment 1 Julien Nabet 2020-05-23 17:51:05 UTC 
With ODBC, which type of database do you use?
Comment 2 altmeier@pca-gmbh.com 2020-05-24 15:51:06 UTC 
Hello 
it is a mariaDB version 5.5.33
Comment 3 Julien Nabet 2020-05-24 19:27:32 UTC 
On pc Debian x86-64 with master sources updated today, I don't reproduce this.
I use:
Package: odbc-mariadb
Source: mariadb-connector-odbc
Version: 3.1.4-1

Package: mariadb-server-10.3
Source: mariadb-10.3
Version: 1:10.3.22-1

I think you must find the way to reproduce this (a specific table for example) unless it's Windows only?
Comment 4 altmeier@pca-gmbh.com 2020-05-28 10:50:17 UTC 
O.K. I agree that this crashes are not so easy:
They occur not reproducable but serveral times per day. Obviously, it occurs only when you have more than one form-document open.
I need to observe the situation more carefully and hope to find a scenario where it happens reproducably. But I am not very optimistic that this will happens.
So, I think this will need time. And probably it is an issue related to the connectors. I use mysql-odbc-connectors with different versions on different computers and probably this results in different affectabilitis.
I will report when I have results.
Comment 5 Buovjaga 2020-09-02 18:39:46 UTC 
It is possible to install older versions in parallel to investigate, if this is a regression:
https://wiki.documentfoundation.org/Installing_in_parallel/Windows

If it is a regression, it is possible to find out the cause:
https://wiki.documentfoundation.org/QA/Bibisect
Comment 6 altmeier@pca-gmbh.com 2020-09-14 17:30:48 UTC 
The instability is in all 6er versions and in the 7.0.
I have all 6er versions deinstalled as working is not possible. We are now using Version 4.4.7.2 which do not have that issue.
In this version (4.4) other problems occur, e.g. a total crash - if a macro tries to focus a dataset within a table which is below 1 or above the maximum table number.
However, that is bad macro-programming and we can avoid that by fixing the bug in the macro.
Comment 7 Julien Nabet 2020-09-14 17:44:13 UTC 
Can't help here=>uncc myself
Comment 8 Alex Thurgood 2021-04-21 10:05:28 UTC 
@altmeier : 

According to the crash report, you're using a 32bit ODBC driver to connect a 64bit version of LO to the mariadb instance ?

Methinks that is surely a recipe for disaster ?

Or is odbc32.dll really a 64bit driver in the present case ?
Comment 9 QA Administrators 2021-10-19 03:42:08 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2021-11-19 05:18:58 UTC 
Dear altmeier@pca-gmbh.com,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp