Summary: | 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 &) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | altmeier <altmeier> |
Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED INSUFFICIENTDATA | ||
Severity: | normal | CC: | buzea.bogdan, ilmari.lauhakangas |
Priority: | medium | Keywords: | possibleRegression |
Version: | 6.0.0.3 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
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 &)"] | Regression By: | |
Bug Depends on: | |||
Bug Blocks: | 133092 |
Description
altmeier@pca-gmbh.com
2020-05-23 14:08:20 UTC
With ODBC, which type of database do you use? Hello it is a mariaDB version 5.5.33 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? 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. 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 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. Can't help here=>uncc myself @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 ? Dear altmeier@pca-gmbh.com, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping 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 |