Bug 90399 - : Mendeley plugin for Writer: Mendeley claims it is LibO's processing of field codes
Summary: : Mendeley plugin for Writer: Mendeley claims it is LibO's processing of fiel...
Status: RESOLVED DUPLICATE of bug 86793
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2015-04-01 15:11 UTC by phaedrusv
Modified: 2015-04-09 16:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description phaedrusv 2015-04-01 15:11:21 UTC
Filed with Mendeley Desktop http://support.mendeley.com/customer/portal/questions/9584677-libreoffice-plugin-is-terribly-slow- 

Problem:
LibO becomes unusable for up to 1 minute while Mendeley plugin assumes control. Top shows soffice.bin consuming >= 50% CPU & ~4.56% Mem

When MD plugin is disabled, or MD closed, there are no issues with LibO. Evidence suggests this is a MD problem.

Document:
Text comprises 433 words (3,026 characters), 7 citations (APA style in text) and corresponding bibliography.

Repeatable issue:
(1) click plugin to inser citation
(2) click into grey citation in text body
(3) click on refresh button

System:
Updated Linux Mint 17, using LibO 4.3.5.2 and MD 1.13.6. AMD Dual core, 64-bit, with 4GB RAM + 2.8 GB dedicated swap partition at 5% swappiness.

The plugin is the correct one for this version of MD; I only have one LibO document open (described above) and the quickstarter enabled.

Have contacted Mendeley Support - response is that this is a problem with LibO fieldcodes: support@mendeley.com replied:

"MAR 31, 2015  |  03:41PM BST
Josh replied:

We don't have an update on this, as it was deemed to be a LO problem in how they process fieldcodes.
Regards,

Josh"
Comment 1 Matthew Francis 2015-04-09 13:30:41 UTC
I wonder if this is anything to do with the issue underlying bug 86793.

A sample document containing one or more of the problematic references would be useful to confirm or exclude this.

@ phaedrusv@gmail.com: Could you possibly attach such a sample document?


Setting Status -> NEEDINFO. Please set it back to UNCONFIRMED when the requested information has been provided.

Thanks!
Comment 2 Matthew Francis 2015-04-09 16:28:30 UTC
Confirmed against a document sent by email that this is caused by the same commit as that identified in bug 86793 comment 10 (Thanks for supplying that)

Closing this one as duplicate.

*** This bug has been marked as a duplicate of bug 86793 ***