Bug 79866 - FILEOPEN: assertion failed crash loading .pptx
Summary: FILEOPEN: assertion failed crash loading .pptx
Status: RESOLVED DUPLICATE of bug 67601
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
(earliest affected) Master
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Keywords: regression
Depends on:
Reported: 2014-06-10 05:17 UTC by tommy27
Modified: 2014-09-30 10:56 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Microsoft Visual C++ Runtime Library error dialog (98.57 KB, image/jpeg)
2014-06-10 05:17 UTC, tommy27

Note You need to log in before you can comment on or make changes to this bug.
Description tommy27 2014-06-10 05:17:14 UTC
Created attachment 100786 [details]
Microsoft Visual C++ Runtime Library error dialog

see Microsoft Visual C++ Runtime Library error dialog in screenshot.

it appears while testing Attachment 97708 [details] for Bug 77746 under Win7x64 in
Build ID: 9266664937251b802e1b48c83f5a76c6767c390f
TinderBox: Win-x86@39, Branch:master, Time: 2014-06-09_10:08:50

4.4 alpha cannot open that file and crashes. can load that file but a "Document in use" dialog appears saying the document is blocked for edit by another system, anyway it allows you to load in.
Comment 1 ign_christian 2014-06-11 03:06:15 UTC
No problem with - Win7 x86, loaded succesfully & no dialog box appeared. Perhaps a regression?
Comment 2 Maxim Monastirsky 2014-06-11 08:28:15 UTC
@tommy27: This assert failing is not a new (I added previous report to 'See also'). But you'll see this only with a debug build, so the fact it works in 4.2.4 doesn't mean it wasn't there. Maybe you could test with a non-deug build (I think tb@42 is producing non-debug ones)?
Comment 3 tommy27 2014-06-11 18:26:14 UTC
retested with Version:
Build ID: 81d2c208a4e6f9df87e2ee70c6e6da146742178a
TinderBox: Win-x86@42, Branch:master, Time: 2014-06-10_23:52:11

no error dialog

Comment 4 Caolán McNamara 2014-09-30 10:56:00 UTC

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