Created attachment 106430 [details] apple generated trace on hang force kill OSX 10.9.4 Latest master build (today 17/09) Mysql connector extension built using : export MARIADBCONFIG="/Volumes/HD1/Shared/Repos/LO/packages/mysql-connector-c-6.1.5-osx10.7-x86_64/bin/mysql_config" --enable-ext-mariadb-connector --with-system-mariadb --enable-bundle-mariadb The extension builds, and is registered with LibreOfficeDev.app during build. I can connect to a remote mysql instance on same LAN, and can open tables for editing. If I try and open a view stored on server, LO hangs. I can execute the view from the same remote connection via the cli. Trace enclosed.
Further investigation reveals that view can be seen, the real problem lies in LO's inability to recover from a dropped connection, e.g. battery power saving on OSX. Even when the remote host is awakened, LO is unable to recover the dropped connection and starts to consume huge amounts of memory. While it is debatable whether LO should try and force a reload of the db context, it shouldn't bomb on the user IMO, even if it does show a timeout message.
Created attachment 106431 [details] crash trace
changed title again to reflect further findings - any attempted table access causes crash after connection error message
Also confirmed on Linux by Heinrich Stollinger on the user mailing list with LO 4352. Changing platform to ALL
Adapted title to reflect behaviour on all platforms
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Still occurs on Version: 5.0.3.2 Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale : fr-FR (fr.UTF-8) OSX 10.11.2
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Testing blocked by bug 107579
Still reproducible with Version: 5.4.1.2 Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group Also reproducible irrespective of the connector - the same problem occurs with the MySQLJDBC connector Changing title to reflect finding
Alex: according to the bt, it should be fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=0297d9cc3b3fb990956cc2f8021a645d3c4fb86f 0 libdbulo.dylib 0x000000011faf039c dbaui::SbaTableQueryBrowser::OnExpandEntry(SvTreeListEntry*) + 76 1 libdbulo.dylib 0x000000011fafbc09 dbaui::DBTreeListBox::RequestingChildren(SvTreeListEntry*) + 41 2 libsvtlo.dylib 0x000000010ba65ebf SvTreeListBox::Expand(SvTreeListEntry*) + 47 3 libsvtlo.dylib 0x000000010ba4da78 SvImpLBox::MakeVisible(SvTreeListEntry*, bool) + 200 4 libdbulo.dylib 0x000000011faf1118 dbaui::SbaTableQueryBrowser::implSelect(rtl::OUString const&, rtl::OUString const&, int, bool, utl::SharedUNOComponent<com::sun::star::sdbc::XConnection, utl::DisposableComponent> const&, bool) + 248 Don't hesitate to reopen this tracker if you still reproduce this with a build including the quoted commit. *** This bug has been marked as a duplicate of bug 112423 ***
Version: 6.0.0.0.alpha0+ Build ID: 80d135922d5a5d0fd0d7178935653870cecf58ea CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group Fixed for me with the above build and co-built connector extension.
I now get the correct error message displayed after a while : MySQL server has gone away