Bug 116689 - Crash in: _GSHandlerCheck_SEH
Summary: Crash in: _GSHandlerCheck_SEH
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:49 UTC by Clemens Prill
Modified: 2019-11-29 03:45 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["_GSHandlerCheck_SEH"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clemens Prill 2018-03-28 23:49:46 UTC
This bug was filed from the crash reporting server and is br-f55b7582-0e93-45dc-b991-75859ae79f07.
=========================================

This issue just happened instantly after starting LibreOffice 6 Writer. It happened directly while the program's loading screen was open (before main window was visible).

Could be related to this one: https://bugs.documentfoundation.org/show_bug.cgi?id=116688
Comment 1 Xisco Faulí 2018-03-29 08:28:36 UTC
Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 2 Clemens Prill 2018-04-03 16:20:29 UTC
I can't test this at the moment because I'm working on important documents and can't mess around with my setup nor find time to set up a test environment.

I highly doubt that this is related to a profile issue.
Comment 3 Buovjaga 2018-04-04 19:32:52 UTC
(In reply to Clemens Prill from comment #2)
> I can't test this at the moment because I'm working on important documents
> and can't mess around with my setup nor find time to set up a test
> environment.
> 
> I highly doubt that this is related to a profile issue.

There is no need to reset the profile: you can simply run LibO in Safe Mode. Either from the Start menu shortcut or Help - Restart in safe mode and then Continue in safe mode.
Comment 4 Clemens Prill 2018-04-09 19:21:57 UTC
I can't reproduce this issue anymore. So it must have been some issue which was related to something else, maybe some Windows 10 or AMD driver update.
Comment 5 Buovjaga 2018-04-09 19:33:53 UTC
(In reply to Clemens Prill from comment #4)
> I can't reproduce this issue anymore. So it must have been some issue which
> was related to something else, maybe some Windows 10 or AMD driver update.

We are still getting these reports, though: https://crashreport.libreoffice.org/stats/signature/_GSHandlerCheck_SEH
Comment 6 Clemens Prill 2018-04-09 19:41:09 UTC
Can this issue/report being related to uninstalling or deactivating third party LibreOffice extensions?
Comment 7 Buovjaga 2018-04-10 06:38:42 UTC
(In reply to Clemens Prill from comment #6)
> Can this issue/report being related to uninstalling or deactivating third
> party LibreOffice extensions?

Might be as there is dp_manager::ExtensionManager::getAllExtensions(com::sun::star::uno::Reference<com::sun::star::task::XAbortChannel> const &,com::sun::star::uno::Reference<com::sun::star::ucb::XCommandEnvironment> const &) 

leading to the crash
Comment 8 Xisco Faulí 2018-05-31 11:06:57 UTC
Hi Clemens Prill,
So in summary, you could only reproduce the crash once?
Comment 9 Clemens Prill 2018-06-06 12:27:27 UTC
(In reply to Xisco Faulí from comment #8)
> Hi Clemens Prill,
> So in summary, you could only reproduce the crash once?

Hello Xisco Faulí, yes, this only happened once. Maybe it is related to the other issue I mentioned in first comment or it is a problem in combination with something that happened before.
Comment 10 Xisco Faulí 2018-06-07 09:27:22 UTC
As you said the crash happened while loading LibreOffice, Do you remember what you were doing before you closed LibreOffice before the crash?
Comment 11 Xisco Faulí 2018-07-09 15:31:11 UTC
(In reply to Xisco Faulí from comment #10)
> As you said the crash happened while loading LibreOffice, Do you remember
> what you were doing before you closed LibreOffice before the crash?

Dear Clemens Prill,
Could you please answer the question above in order to help us triage this issue?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the question has been answered
Comment 12 Clemens Prill 2018-07-09 16:14:25 UTC
(In reply to Xisco Faulí from comment #11)
> (In reply to Xisco Faulí from comment #10)
> > As you said the crash happened while loading LibreOffice, Do you remember
> > what you were doing before you closed LibreOffice before the crash?
> 
> Dear Clemens Prill,
> Could you please answer the question above in order to help us triage this
> issue?
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the question has been answered

Hello Xisco Faulí,


I'm sorry for the late reply! I thought I did reply but it seems like I forgot to submit it last time ... I did uninstall Mendeley Desktop's extension (https://www.mendeley.com/download-desktop/) and installed Zotero with its extension (https://www.zotero.org/).
Comment 13 Dieter 2018-12-06 10:56:11 UTC
(In reply to Clemens Prill from comment #12)
> I'm sorry for the late reply! I thought I did reply but it seems like I
> forgot to submit it last time ... I did uninstall Mendeley Desktop's
> extension (https://www.mendeley.com/download-desktop/) and installed Zotero
> with its extension (https://www.zotero.org/).

So that means, that the bug is no longe reproducible for you and - regarding to Xisco's question in comment 10 - you don't rember what you were doing before the crash. So should we close this bug?

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' or to RESOLVED INSUFFICENTDATA.
Comment 14 Clemens Prill 2018-12-06 11:58:35 UTC
(In reply to Dieter Praas from comment #13)
> So that means, that the bug is no longe reproducible for you and - regarding
> to Xisco's question in comment 10 - you don't rember what you were doing
> before the crash. So should we close this bug?

I did uninstall Mendeley Desktop's extension (https://www.mendeley.com/download-desktop/) and installed Zotero with its extension (https://www.zotero.org/). After that I did restart LibreOffice as suggested (like always when you install/uninstall an extension) and it crashed like reported here. This is all I did before this crash occurred.
Comment 15 Dieter 2019-05-01 05:03:01 UTC
There is no crash with this signature in LO 6.2. (see https://crashreport.libreoffice.org/stats/signature/_GSHandlerCheck_SEH).

Clemens, can you still reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 16 QA Administrators 2019-10-29 03:30:08 UTC Comment hidden (obsolete)
Comment 17 QA Administrators 2019-11-29 03:45:33 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