Created attachment 60424 [details]
ADocument.odt

I'm sorry but I can't reproduce this problem; for me, export as PDF works with LibreOffice 3.5.2.2 (on MacOS X 10.6.8) like before. This means, the information given in the original report is not enough to reproduce this problem.

Could you, please,
-- provide a sample file which you can't export as PDF? Or do you see this problem with all files? Which file types did you use: ODT documents, DOC files, DOCX files?
-- tell us which settings you use in the 'Export as PDF ...' dialog? Just the default settings, or did you change some setttings?
-- tell us which operating system you use (Windows? which version? which language?)?

Hi,

I've completely forgotten I submitted this bug!!!
No problem, I'm going to tell you all the stuff again(I don't quite 
remember what I submitted to bugzilla).

Some files were exported into pdf format well by Writer, others not. I 
wasn't able to figure out what caused the problem.
The document I used is the odt template used to compile European 
Curriculume Vitae (english version), you can find it here 
<http://europass.cedefop.europa.eu/en/documents/curriculum-vitae/templates-instructions>.
I downloaded it the first time and each time I need to compile a new cv 
I do a copy of it. After, I export it as pdf format.
When I do this operation with Writer, sometimes it crashes. Reloading 
the file again Writer is able to recover the document.
I attached the file for your reference. I removed all private data.

That file is on an external hard disk. I have all access, writing 
reading deleting etc, on that hard disk. When I do these operations I'm 
logged in as administrator.
However, when I create a new folder in that hard disk, for example, the 
os asks me the administration permission to do that.
My LibreOffice version is 3.5.2.2.
I use the default settings during the export.
My OS: Windows 7 ( 64 bit ), english.

Note: OpenOffice Writer doesn't suffer from the same problem.

Feel free to ask me techinical questions too, I'm a software developer.

Thanks


On 4/21/2012 4:20 PM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> Roman Eisele<bugs@eikota.de>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |bugs@eikota.de
>
> --- Comment #1 from Roman Eisele<bugs@eikota.de>  2012-04-21 07:20:55 PDT ---
> I'm sorry but I can't reproduce this problem; for me, export as PDF works with
> LibreOffice 3.5.2.2 (on MacOS X 10.6.8) like before. This means, the
> information given in the original report is not enough to reproduce this
> problem.
>
> Could you, please,
> -- provide a sample file which you can't export as PDF? Or do you see this
> problem with all files? Which file types did you use: ODT documents, DOC files,
> DOCX files?
> -- tell us which settings you use in the 'Export as PDF ...' dialog? Just the
> default settings, or did you change some setttings?
> -- tell us which operating system you use (Windows? which version? which
> language?)?
>

@codevisio:
Thank you very much for your detailed description! With the information given by you it should be much easier now to track down this bug. I will investigate a bit and try to reproduce it.

Similar to bug 46256 - "LibreOffice 3.5 Writer crashes when making PDF". But it is hard to say whether this is the same bug or just a similar one. So I don't think we should mark one of these bugs as duplicate.

I have spent some hours trying to reproduce this bug. According to comment #2, I got a copy of the European Curriculume Vitae template, ODT version, and tried to export it to PDF. But everything worked as expected. I tried to fill in various valid and invalid values in the template, I intserted pictures etc., but still no crash.

It is possible that I missed some minor point which makes the difference, e.g., some special formatting. But for now, the most probable possibility is just that this bug is specific to LibreOffice running on Windows, maybe even to Windows 7 (64 bit). I did my tests on MacOS X, and if there is some OS-dependence within this bug, it is necessary that I could not reproduce it. Therefore:

-> Changing Platform to 'Windows' for now.

-> Could please someone else who uses Windows 7 try to reproduce this bug?

Hi Roman,

Maybe I could help.

In those hard cases, in my professional life, and with the user's help,
I usually put some "output debug information" before and after potential
problematic code. This "output debug information" could be
in the form of some pre/post condition around the problematic code and 
written into a log file
or in the form of message boxes during program running, or
whatever helps you. The better is to provide, at the beginning of 
program development stage, the code of your project filled with
log-debug information to be activated launching your program for example 
in debug mode but I don't know if this is the case with Writer.
Actually I don't have time to debug Writer code via visual studio or 
through WinDBG or through assembler or alike,
but if you are able to do a test-release of Writer with my above 
suggestions (a few infor written in the log file or messages boxes)then 
I'll be available to make a test stage
for you.

Let me know. Thanks

On 4/27/2012 10:51 AM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> Roman Eisele<bugs@eikota.de>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           OS/Version|All                         |Windows (All)
>             Severity|normal                      |major
>
> --- Comment #5 from Roman Eisele<bugs@eikota.de>  2012-04-27 01:51:29 PDT ---
> I have spent some hours trying to reproduce this bug. According to comment #2,
> I got a copy of the European Curriculume Vitae template, ODT version, and tried
> to export it to PDF. But everything worked as expected. I tried to fill in
> various valid and invalid values in the template, I intserted pictures etc.,
> but still no crash.
>
> It is possible that I missed some minor point which makes the difference, e.g.,
> some special formatting. But for now, the most probable possibility is just
> that this bug is specific to LibreOffice running on Windows, maybe even to
> Windows 7 (64 bit). I did my tests on MacOS X, and if there is some
> OS-dependence within this bug, it is necessary that I could not reproduce it.
> Therefore:
>
> ->  Changing Platform to 'Windows' for now.
>
> ->  Could please someone else who uses Windows 7 try to reproduce this bug?
>

@codevisio (comment #6):
Thank you very much for your helpful offer! But given the fact that I don't have any experience with debugging on Windows (I'm not an actual developer, just someone helping out a little bit with QA issues) I can't help here.

Therefore, I have reported this issue and your friendly offer to the LibreOffice QA mailing list. I hope that someone with experience in debugging LibreOffice on Windows will contact you soon.

Thank you very much again!

Win7x64Ultimate, LibreOffice 3.5.3RC2

I can't reproduce with the attached document, neither with the .odt and .doc English version, downloaded from the comment 2 link.

Some more related/duplicate bug reports:
Bug 39041 - "WRITER PDF Export with bookmarks crashes"
Bug 32771 - "Writer crashes while exporting big PDF file."
Bug 46750 - "PDF export crash on ODT document"
Bug 46891 - "CRASH when PDFEXPORT"

From the count of similar reports/duplicates I suppose we have a real problem
with PDF export from Writer in LibreOffice 3.5.x, but it is hard to track it
down ...

Hi,

it's not hard to track it down from my opinion, it needs a little 
organization only.

As I said some days ago I can help.

Is there any developer out there available to take this issue?
If so, please contact me.





On 4/30/2012 6:11 PM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> --- Comment #9 from Roman Eisele<bugs@eikota.de>  2012-04-30 09:11:04 PDT ---
> Some more related/duplicate bug reports:
> Bug 39041 - "WRITER PDF Export with bookmarks crashes"
> Bug 32771 - "Writer crashes while exporting big PDF file."
> Bug 46750 - "PDF export crash on ODT document"
> Bug 46891 - "CRASH when PDFEXPORT"
>
>  From the count of similar reports/duplicates I suppose we have a real problem
> with PDF export from Writer in LibreOffice 3.5.x, but it is hard to track it
> down ...
>

Created attachment 60902 [details]
DebugSessionFromWinDBG.txt

Checked with:
LOdev 3.5.3rc1+ 
Build ID: 51648779-22e3d74-d554af7
Windows 7 Professional SP1 64 bit

Could not reproduce with attached file.

(In reply to comment #10)
> Hi,
> it's not hard to track it down from my opinion, it needs a little 
> organization only.
> As I said some days ago I can help.
> Is there any developer out there available to take this issue?
> If so, please contact me.

Debug screencast: 
http://lists.freedesktop.org/archives/libreoffice/2012-March/027979.html

Debug builds: 
http://dev-builds.libreoffice.org/win32-debug/libreoffice-3-5/

Hope the author of these will make full step by step debug wiki article some day...
Unfortunately seems he is not available at the moment - not answered yet to this posting:
http://nabble.documentfoundation.org/Libreoffice-qa-How-to-get-backtrace-on-Windows-tp3922989.html

Hi,

thank you for you information.

I installed one of the release candidate from your link.

Although building a release with debug symbols is a good idea, provide 
it without pdb files will not take us too far.

I downloaded and installed this one 
LibO-Dev_3.5.3rc1_Win_x86_install_en-US.msi.

Could you make available the pdb files produced during the compilation 
of that build release too?

However,
I debugged anyway Writer with WinDBG and Visual Studio debugger and I 
wrote the output content of the
debugging sessions into txt files. The tht files are in attach to this 
email. They are not so usufel in my opinion, because the missing of the 
pdb files above
and the source code used to build that release.

Let me know how do you want to proceed.

Thank you



On 5/2/2012 10:08 AM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> --- Comment #11 from bfoman<bfo@mailinator.com>  2012-05-02 01:08:58 PDT ---
> Checked with:
> LOdev 3.5.3rc1+
> Build ID: 51648779-22e3d74-d554af7
> Windows 7 Professional SP1 64 bit
>
> Could not reproduce with attached file.
>
> (In reply to comment #10)
>> Hi,
>> it's not hard to track it down from my opinion, it needs a little
>> organization only.
>> As I said some days ago I can help.
>> Is there any developer out there available to take this issue?
>> If so, please contact me.
> Debug screencast:
> http://lists.freedesktop.org/archives/libreoffice/2012-March/027979.html
>
> Debug builds:
> http://dev-builds.libreoffice.org/win32-debug/libreoffice-3-5/
>
> Hope the author of these will make full step by step debug wiki article some
> day...
> Unfortunately seems he is not available at the moment - not answered yet to
> this posting:
> http://nabble.documentfoundation.org/Libreoffice-qa-How-to-get-backtrace-on-Windows-tp3922989.html
>

Created attachment 60903 [details]
DebugSessionFromWisualStudio2008txt.txt

Tor, Andras, could you please give codevisio some hints how to debug this problem on Windows?

codevisio, it seems that you are interested into debugging this problem. If you are in doubts, the best way is to ask on the developer mailing list libreoffice@lists.freedesktop.org or on the irc channel #libreoffice-dev at irc.freenode.net.

I add also some Writer experts into CC. They might give some code pointers if needed.

Follow jcorrius's advice? http://www.youtube.com/watch?v=fppBTs215yc

I already done that.
Look at my last comments in the mail chain here
https://bugs.freedesktop.org/show_bug.cgi?id=47511

I followed the jcorrius advice and produced the two txt files.

However, jcorrius is able to do that, what you can see in the video,  
because:
1) it has the source tree of libreoffice on its local dev machine
2) it has the pdb files prduced from the compilation process

The txt files I sent are more or less what jcorrius did, without the 
source code and without the pdb files.
I don't know if my txt files will be useful. From my experience and from 
the debugging session I did it seems to me that there some code 
exceptions during the
export to pdf execution feature.

If someone provides the following:
1) the build release with debugging symbols inside (already done by 
jcorrius and downloadable from 
http://dev-builds.libreoffice.org/win32-debug/libreoffice-3-5/ ).
+
2) the libreoffice pdb files produced during the build of the release in 
point 1).
+
3) the source code, in a downloadable form, s/he used to create the 
release from point 1).

I'll be able to do the exact jcorrius did in the video.

Let me know. I'm available to do that.

Thanks



On 5/3/2012 11:05 AM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> --- Comment #16 from Tor Lillqvist<tlillqvist@suse.com>  2012-05-03 02:05:59 PDT ---
> Follow jcorrius's advice? http://www.youtube.com/watch?v=fppBTs215yc
>

Let's invite him then...

(In reply to comment #17)

@codevisio:

The stack trace looks quite good already :)

Do you have a valid MSDN license? If you do I can give you the link to my Build Virtual Machine which has everything you need.

Cheers,

J.

good! I didn't know if the txt files were sufficient.
Well, let me know if you need more test or more help, just let me know.

Yes, I had the msdn licence in the past.
No, thank you. I'd like to help open source projects, both in testing 
and coding,
but looking for a new job is taking too much time and I haven't found 
anything yet.

I'd like to point you to another little issue, it's not a blocking one, 
but it could be useful to fix it.

-Load an odt document from a folder.
-Try to export is as pdf file.
-The PDF Options dialog willl appear.
-Leave it as it is with the default options and click on the Export button.
-The Export dialog will appear (the traditional win32 open save common 
dialog) with the suggested name for the pdf.
The suggested name for the pdf document is the same as the document 
loaded with extension changed to pdf, this is good.
However, the folder suggested from this dialog is the old one, that is 
the folder where you exported an odt document as  pdf the last time you 
exported it,
and not the folder from which the current odt document was loaded. It 
would be useful if the folder selected was the same of the odt document 
you loaded into Writer.
If I don't wrong remember OpenOffice take care of this, but I'm not sure.

Let me know if you need more.

Good work!






On 5/3/2012 12:05 PM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> --- Comment #19 from Jesus Corrius<jesus@softcatala.org>  2012-05-03 03:05:02 PDT ---
> (In reply to comment #17)
>
> @codevisio:
>
> The stack trace looks quite good already :)
>
> Do you have a valid MSDN license? If you do I can give you the link to my Build
> Virtual Machine which has everything you need.
>
> Cheers,
>
> J.
>

(In reply to comment #19)
> (In reply to comment #17)
> > @codevisio:
> > The stack trace looks quite good already :)
> 
> Do you have a valid MSDN license? If you do I can give you the link to my Build
> Virtual Machine which has everything you need.

Seems some errors in LO are Windows 7 specific. Is your VM a Windows 7 edition?

Microsoft is delivering free Windows XP/Vista/7 VHD builds (available at http://www.microsoft.com/en-us/download/details.aspx?id=11575), so maybe with free Visual Studio 2008 Express one could build a debug dev station by oneself. 
Is it possible that you could check if http://wiki.documentfoundation.org/Development/Native_Build and http://wiki.documentfoundation.org/Development/Windows_Build_Dependencies are up to date and have all informations needed to build LOdev 3.5.x? That would be great for all Windows 7 wannabe testers and IMHO would help a project a lot. Thanks in advance! :)

00a8a93c 6ddd5d0c 00a8ab44 4f0f20e5 00000001 vcllo!WorkWindow::IsMaximized+0x3e6e0
00a8aacc 6ddd5736 0ed73a18 00a8ab44 4f0f2199 vcllo!OutputDevice::ImplGlyphFallbackLayout+0x2cc

looks the most suspicious to me. There shouldn't be any way ImplGlyphFallbackLayout calls WorkWindow::IsMaximized so the problem might be in there.

Created attachment 61087 [details]
valgrind log under linux

These are the valgrind-under-Linux warnings. I sort of think the problem lies elsewhere from these, but these are the low-hanging fruits worth fixing anyway.

If the windows crash is related to glyph fallback, then ideally we could get a list of fonts installed on the windows box in order to be sure we can replicate the same environment. I wonder if there is a trivial equivalent to fontconfig's fc-list for windows to get a straight-forward list of the fonts installed ?

http://cgit.freedesktop.org/libreoffice/core/commit/?id=c2003c73d71001fcb66fb86a15cde82e60aa242a fixes the substantive valgrind warning anyway

Hi,

who developer are trying to fix this bug? Jesus Corrius?

thanks

On 5/3/2012 12:05 PM, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=47511
>
> --- Comment #19 from Jesus Corrius<jesus@softcatala.org>  2012-05-03 03:05:02 PDT ---
> (In reply to comment #17)
>
> @codevisio:
>
> The stack trace looks quite good already :)
>
> Do you have a valid MSDN license? If you do I can give you the link to my Build
> Virtual Machine which has everything you need.
>
> Cheers,
>
> J.
>

(In reply to comment #22)
> 00a8a93c 6ddd5d0c 00a8ab44 4f0f20e5 00000001
> vcllo!WorkWindow::IsMaximized+0x3e6e0
                                ^^^^^^^
the 0x3e6e0 offset looks unrealistically large to me,
probably the stack trace is wrong, some missing symbols...

> 00a8aacc 6ddd5736 0ed73a18 00a8ab44 4f0f2199
> vcllo!OutputDevice::ImplGlyphFallbackLayout+0x2cc
> 
> looks the most suspicious to me. There shouldn't be any way
> ImplGlyphFallbackLayout calls WorkWindow::IsMaximized so the problem might be
> in there.

@ alix.helme-guizon@numericab:

Thank you for confirming that this bug is still reproducible with LibreOffice 3.6.0.4! However, if you find that a bug is still reproducible with a newer version, please just leave an additional comment about this, but do not "update" the Version field: we use the Version field for the FIRST version in which a bug is known to exist (is reproducible), and NOT the newest one. Thank you!

I can reproduce this bug in Libo 4 (Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
Win 7 32bits sp1

The interesting in this bug I have seen :
- save Adocument on desktop, dubble-clic on it to open, Clic On pdf => crash

Workaround :
- Open Libo first, File-open Adocument, clic on pdf => OK !

So I think there is a little difference with the opening methods :-/
Hope that's could help to see where is the problem.

Yves.

I couldn't reproduce this with LO 4.2.5.1 (or even 4.0.5 or 3.6.7). It was probably fixed some time ago. 
Since it's rather old, I close as WORKSFORME.