LibreOffice 4.0.2 / 4.0.3 /4.1.0 very slow when access forms with Parent-Child (subform) relationships

Bug #1185463 reported by SAS_Argentina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LibreOffice
Invalid
Medium
libreoffice (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Several days ago I upgrade from Ubuntu 12.04 to 13.04.
Original repositories changes releases of LibreOffice and updated it

When access to forms with Forms/Subforms combination (Parent-Child Relationship) the parent record display fine but the subform data display takes long time (4 secs before update to 40 secs with the upgrade)

I changed from 4.0.2 (official repository) to downlodable 4.0.3 and turn worst.
I changed ODBC and drivers from MySQL and the same result.
I reinstall MySQL server to avoid DB-Tables perfomance issues.
I checked CPU usage and almost takes 100% when navigated thru records

I had to downgrade to LO 3.6.6 version and works as expected (as long as Ubuntu 12.04).

At present time I use:

Ubuntu release 13.04
MySQL 5.5.31

Any Ideas?

penalvch (penalvch)
tags: removed: 13.04 4.x downgrade libreoffice slow upgrade
penalvch (penalvch)
tags: added: raring regression-release
Revision history for this message
In , Björn Michaelsen (bjoern-michaelsen) wrote :

When access to forms with Forms/Subforms combination (Parent-Child Relationship) the parent record display fine but the subform data display takes long time (4 secs before update to 40 secs with the upgrade)

I changed from 4.0.2 (official repository) to downlodable 4.0.3 and turn worst.
I changed ODBC and drivers from MySQL and the same result.
I reinstall MySQL server to avoid DB-Tables perfomance issues.
I checked CPU usage and almost takes 100% when navigated thru records

I had to downgrade to LO 3.6.6 version and works as expected (as long as Ubuntu 12.04).

At present time I use:

Ubuntu release 13.04
MySQL 5.5.31

Revision history for this message
In , Björn Michaelsen (bjoern-michaelsen) wrote :

see downstream bug for details

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

So to clarify:
- 3.6.6 works reasonably quick (4sec)
  - Question: 3.6.6 from the LibreOffice PPA or the TDF build?
- 4.0.2 as released with Ubuntu 13.04 (raring) is slower
- 4.0.4 is even more slow
  - Question: 4.0.4 from the PPA or 4.0.4 from libreoffice.org?

Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
SAS_Argentina (sergio-sosa) wrote :

Thanks Björn,

I downloaded from libreoffice.org.

When installed 4.0.4 I downloaded from libreoffice.org.

A couple of days ago, I reinstalled from Ubuntu repository and still slow (2x time from 3.6.6 or 3.6.7.- I have tested in 2 equipment). Now I have installed 3.6.7 from libreoffice.org (deb files) and works fine.

Revision history for this message
In , Nv4y-robert (nv4y-robert) wrote :

I have just tried it with the LO 4.1.0.4-packages of OpenSUSE 12.3 64bit rpm (downloaded from OpenSUSE).
Had a table with 2 columns and 36 rows in the mainform and a table 31 columns and 9000 rows in the subform. When I change the row in the mainform the data in the subform appear immediately.
So I can't confirm this bug. I can't test the original LO 4.* together with ODBC, because LO will shutdown immediately when the connection should be enabled (see https://bugs.freedesktop.org/show_bug.cgi?id=65830 )

Revision history for this message
In , Qubit (qubit) wrote :

Looks like we can't confirm a regression, even after testing. Changing 'regression' -> 'PossibleRegression' until we have independent confirmation of a regression.

Bjoern: Please ask downstream OP to test against 4.1/daily build.

Changed in df-libreoffice:
status: New → Incomplete
Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear Bug Submitter,

Please read the entire message before proceeding.

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here:
https://wiki.documentfoundation.org/QA/FDO/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

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO

Changed in df-libreoffice:
status: Incomplete → Invalid
Revision history for this message
Rolf Leggewie (r0lf) wrote :

works fine for me

Changed in libreoffice (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.