Bug 83995 - CRASH - when attempting to open remote mysql table using native connector with connection timeout
Summary: CRASH - when attempting to open remote mysql table using native connector wit...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
Version: 4.3.5.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 13:34 UTC by Alex Thurgood
Modified: 2015-01-05 07:40 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
apple generated trace on hang force kill (482.68 KB, text/plain)
2014-09-17 13:34 UTC, Alex Thurgood 		Details
crash trace (78.48 KB, text/plain)
2014-09-17 13:54 UTC, Alex Thurgood 		Details
View All

Description Alex Thurgood 2014-09-17 13:34:20 UTC 
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.
Comment 1 Alex Thurgood 2014-09-17 13:50:00 UTC 
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.
Comment 2 Alex Thurgood 2014-09-17 13:54:14 UTC 
Created attachment 106431 [details]
crash trace
Comment 3 Alex Thurgood 2014-09-17 13:55:46 UTC 
changed title again to reflect further findings - any attempted table access causes crash after connection error message
Comment 4 Alex Thurgood 2015-01-05 07:38:37 UTC 
Also confirmed on Linux by Heinrich Stollinger on the user mailing list with LO 4352.

Changing platform to ALL
Comment 5 Alex Thurgood 2015-01-05 07:40:26 UTC 
Adapted title to reflect behaviour on all platforms

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.