Bug 93153 - Windows 10 x64 When I exit Writer without saving the document, I get the attached C++ error
Summary: Windows 10 x64 When I exit Writer without saving the document, I get the atta...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-05 18:00 UTC by James Olson
Modified: 2017-10-30 10:50 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
jpg showing C++ error (30.45 KB, image/jpeg)
2015-08-05 18:00 UTC, James Olson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Olson 2015-08-05 18:00:39 UTC
Created attachment 117683 [details]
jpg showing C++ error

I use finereader 12 to scan information into writer. From writer I copy it into an other program Sigil. After saving in Sigil, I close the Writer document without saving it. I then get the C++ error shown in the attached jpg. Error R6025 pure virtual function call.
Comment 1 Joel Madero 2015-08-05 18:27:45 UTC
This is an extreme case of "corner-case". . . going to be really hard to find anyone to reproduce this issue.

Does this error come up at *any other time*? If not, it could sit UNCONFIRMED for a long long time....

Also are those other pieces of software free? If they are not, we'll likely close this as WONTFIX because it's not QA's job to purchase software to figure out some crazy corner case issue. If they are free, can you provide links to them? If they are not free, I suggest considering getting paid support as it's likely the only way that this kind of corner case issue would be fixed (outside of you fixing it yourself).
Comment 2 James Olson 2015-08-05 18:50:43 UTC
This only began to happen after I upgraded from Windows 7 to Windows 10
Comment 3 Joel Madero 2015-08-05 19:16:06 UTC
Unfortunately that doesn't answer any of my questions....
Comment 4 Buovjaga 2015-09-01 17:58:47 UTC
Sigil is GPL: https://github.com/Sigil-Ebook/Sigil/releases
Finereader is proprietary & commercial.

It seems to be an issue of Win 10 upgrade messing things up.
Comment 5 Adolfo Jayme Barrientos 2016-04-28 04:21:04 UTC
Also, please try upgrading to the latest stable release available (which is 5.1.3 right now) https://www.libreoffice.org/download/libreoffice-fresh/?type=win-x86_64&version=5.1.3&lang=en
Comment 6 tommy27 2017-01-13 17:45:54 UTC
5.2.4.2 is available.
please retest and give feedback.
if bug is gone change status to RESOLVED WORKSFORME 
if bug is still present revert it to UNCONFIRMED

status NEEDINFO until then.
Comment 7 Chris Sherlock 2017-03-11 07:50:13 UTC
That error is a pure call runtime error from Visual C++. 

Somehow, somewhere in LO we have either a constructor or a destructor calling a pure virtual function. 

I actually didn't think this could be possible, but apparently you can actually mark a function as a pure virtual function and have a defined function body! Which is insane really, and in C++ This is undefined/implementation specific behaviour. How we locate this, however, might be tricky. 

It would be good to have the source document created from FineReader. Perhaps we could trigger the error!
Comment 8 QA Administrators 2017-09-29 08:57:18 UTC Comment hidden (obsolete)
Comment 9 Xisco Faulí 2017-10-30 10:50:53 UTC
Dear Bug Submitter,

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-20171030