Bug 115764 - Crash in: google_breakpad::ExceptionHandler::HandlePureVirtualCall() with OpenGL enabled
Summary: Crash in: google_breakpad::ExceptionHandler::HandlePureVirtualCall() with Ope...
Status: RESOLVED DUPLICATE of bug 115420
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: x86-64 (AMD64) Windows (All)
: highest normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-15 23:40 UTC by jorortega
Modified: 2018-02-23 19:15 UTC (History)
4 users (show)

See Also:
Crash report or crash signature: ["google_breakpad::ExceptionHandler::HandlePureVirtualCall()"]

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jorortega 2018-02-15 23:40:07 UTC 
This bug was filed from the crash reporting server and is br-7dc50b0e-4f9f-46a7-b383-1f55be1491c1.
=========================================

To reproduce the crash:

Open Libreoffice
go to extensions
look for updates
press close
Crash.
Comment 1 Julien Nabet 2018-02-16 09:07:40 UTC 
Could you take a look to https://wiki.documentfoundation.org/QA/FirstSteps and give it a try?
Indeed, it could be a LO profile pb or OpenGL for instance.
Comment 2 jorortega 2018-02-16 15:58:25 UTC 
Steps taken, crash is always there.

Detail:

Pressing the "X" to close the window doesn't crash, it closes the window normally. Pressing the "CLOSE" button crashes it.
Comment 3 Julien Nabet 2018-02-18 09:17:18 UTC 
Thank you for your feedback, since I don't have more questions, I'll put this one back to UNCONFIRMED
Comment 4 Telesto 2018-02-18 15:15:10 UTC 
Repro with
Version: 6.1.0.0.alpha0+
Build ID: b87fe45e8b087a315a65b92bf9c168b1e4c5cc00
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-02-16_23:14:35
Locale: nl-NL (nl_NL); Calc: CL
Comment 5 Timur 2018-02-19 14:30:32 UTC 
There was already Bug 115476, please check.
Comment 6 Telesto 2018-02-19 14:46:26 UTC 
(In reply to Timur from comment #5)
> There was already Bug 115476, please check.

Probably the same bug. However this bug has straight forward steps to reproduce the issue. And nobody did confirm bug 115476, based on a repro. So adding bug 115476 as dupe seems a better solution.
Comment 7 V Stuart Foote 2018-02-19 21:57:01 UTC 

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