Bug 116688 - Crash in: BigPtrArray::Index2Block(unsigned __int64) when disabling Mendeley extension
Summary: Crash in: BigPtrArray::Index2Block(unsigned __int64) when disabling Mendeley ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-28 23:47 UTC by Clemens Prill
Modified: 2020-02-26 02:47 UTC (History)
4 users (show)

See Also:
Crash report or crash signature: ["BigPtrArray::Index2Block(unsigned __int64)"]


Attachments
Mendeley extension (35.54 KB, application/zip)
2018-04-10 19:19 UTC, Buovjaga
Details
Zotero extension (1.87 MB, application/vnd.openofficeorg.extension)
2018-04-11 11:27 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Clemens Prill 2018-03-28 23:47:12 UTC
This bug was filed from the crash reporting server and is br-9cbafd09-d3b3-413c-91e7-18baf28d031d.
=========================================

This crash occurred instantly after I clicked on the button to disable the Mendeley Desktop's LibreOffice extension in extension manager. I'm not sure it is related to this specific extension or if it is a problem because I had Mendeley Desktop's extension active and also Zotero's one which serves the same purpose. Both are software solutions to manage your literature and bibliography in a professional way.
Comment 1 Clemens Prill 2018-03-28 23:55:10 UTC Comment hidden (off-topic)
Comment 2 Clemens Prill 2018-03-28 23:56:13 UTC Comment hidden (off-topic)
Comment 3 Xisco Faulí 2018-03-29 08:27:05 UTC
is it possible to use the Mendeley plugin for free? if so, from where can I download it ?
Comment 4 Clemens Prill 2018-03-29 09:04:24 UTC
You can download the software for free at the main page of this site and this link will show you where the install button for the extension is: https://www.mendeley.com/guides/using-citation-editor/01-installing-citation-plugin
Comment 5 Buovjaga 2018-04-10 19:19:57 UTC
Created attachment 141270 [details]
Mendeley extension

I downloaded from here and extracted: https://www.mendeley.com/download-desktop/

In the Linux version it was in share/mendeleydesktop/openOfficePlugin

I could not repro the crash on Linux. Will try on Windows next.

Arch Linux 64-bit
Version: 6.1.0.0.alpha0+
Build ID: d4c0e7ef2b7f7e3cb36996bad72ac255b630beb4
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on April 8th 2018

Arch Linux 64-bit
Version: 6.0.2.1.0+
Build ID: 6.0.2-1
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Comment 6 Buovjaga 2018-04-10 19:22:13 UTC
No problem on Windows either.

Note that I did not have the Mendeley desktop installed - only the extension. I hope this is enough. After all, they say "To use Mendeley you’ll need to register"

Version: 6.0.3.2 (x64)
Build ID: 8f48d515416608e3a835360314dac7e47fd0b821
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: fi-FI (fi_FI); Calc: group
Comment 7 Clemens Prill 2018-04-10 20:54:56 UTC
Try to install Zotero (https://www.zotero.org/) additionally next to Mendeley. Maybe the conflict happens if both is active and you disable Mendeley.
Comment 8 Buovjaga 2018-04-11 11:27:43 UTC
Created attachment 141282 [details]
Zotero extension

No problem on Win even with Zotero alongside.
Comment 9 Thomas Lendo 2018-04-12 12:57:41 UTC
It may have nothing to do with the bug opener's report but I had a crash in 5.4 with the same crash summary today: br-60f430c8-da3e-4863-8b3d-23f058bcfd38

Reason was the revert/undo of a bunch of copying and formatting actions from an ODF file which formatting was destroyed by MSO Word.
Comment 10 Timur 2018-04-12 14:49:26 UTC
https://crashreport.libreoffice.org/stats/signature/BigPtrArray::Index2Block%28unsigned%20__int64%29 shows 2349 reports, Windows x64. Not likely to be caused by not so frequent Mendeley.
Mendeley has some long-standing bugs, we need volunteers to triage them.
Comment 11 Xisco Faulí 2018-05-31 11:56:34 UTC
(In reply to Thomas Lendo from comment #9)
> It may have nothing to do with the bug opener's report but I had a crash in
> 5.4 with the same crash summary today:
> br-60f430c8-da3e-4863-8b3d-23f058bcfd38
> 
> Reason was the revert/undo of a bunch of copying and formatting actions from
> an ODF file which formatting was destroyed by MSO Word.

Hi Thomas Lendo,
it would be really nice if you could try to reproduce it again... having steps to reproduce it is key in order to fix this crash...
Comment 12 Thomas Lendo 2018-09-25 11:26:39 UTC
(In reply to Xisco Faulí from comment #11)
Xisco, my crashes are caused by bug 117215 or/and bug 117444. I've no Mendeley extension installed.
Comment 13 Dieter 2019-05-01 04:56:27 UTC Comment hidden (obsolete)
Comment 14 Dieter 2019-05-01 05:01:45 UTC Comment hidden (obsolete)
Comment 15 Dieter 2019-07-29 11:23:59 UTC
Triaging bug 126583 I saw, that there is no crash report in LO 6.2.5 with the signature ["BigPtrArray::Index2Block(unsigned __int64)"]. So is this bug fixed or still reproducible in latest version?
Comment 16 QA Administrators 2020-01-26 03:31:29 UTC Comment hidden (obsolete)
Comment 17 QA Administrators 2020-02-26 02:47:17 UTC
Dear Clemens Prill,

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