Apache OpenOffice (AOO) Bugzilla – Issue 123452
Crash exporting tagged PDF
Last modified: 2017-05-20 10:14:53 UTC
Created attachment 81734 [details] Writer document that crashes AOO 4.0.1 if exporting to PDF When exporting a particular writer document to PDF, using the pdf-export icon, AOO 4.0.1 crashes.
(In reply to rony from comment #0) > When exporting a particular writer document to PDF, using the pdf-export > icon, AOO 4.0.1 crashes. Please try the PDF export dialog from "File" - "Export as PDF..." Is PDF/A-1a checked? I can reproduce the crash with a new user profile only if a check that option. With the default options it does not crash. To test with a new user profile and its default options, run soffice.exe from within cmd.exe and pass -env:UserInstallation=FILE_URL_TO_USER_DIR, for example: C:\>"C:\Archivos de programa\OpenOffice 4\program\soffice.exe" -env:UserInstallation=file:///C:/tmpaoo and don't migrate settings from 3.* user profile.
Created attachment 81737 [details] Debugger stack trace The crash happens in http://svn.apache.org/viewvc/openoffice/trunk/main/sw/source/core/text/EnhancedPDFExportHelper.cxx?revision=1525917&view=markup#l379 dereferencing an invalid iterator, so the following solves the crash: const FrmTagIdMap::const_iterator aIter = rFrmTagIdMap.find( pKey ); if ( aIter != rFrmTagIdMap.end() ) nReopenTag = (*aIter).second;
Not reproducible on Linux. May be "regression" introduced be stlport removal. Setting hdu on Cc
Duplicated. *** This issue has been marked as a duplicate of issue 122928 ***
(In reply to Ariel Constenla-Haile from comment #2) > The crash happens in > http://svn.apache.org/viewvc/openoffice/trunk/main/sw/source/core/text/ > EnhancedPDFExportHelper.cxx?revision=1525917&view=markup#l379 > dereferencing an invalid iterator, so the following solves the crash: > > const FrmTagIdMap::const_iterator aIter = rFrmTagIdMap.find( pKey ); > if ( aIter != rFrmTagIdMap.end() ) > nReopenTag = (*aIter).second; This fix is incidentally the same as the one I suggested in attachment 81699 [details] to fix bug 123409. With both issues having the same root cause I'm adjusting the duplicate number. *** This issue has been marked as a duplicate of issue 123409 ***
.