Created attachment 96653 [details] The error that is shown to the user. Problem description: Pure Virtual Function call r6025 when closing a read-only document (opened on PowerBuilder through automation)using the closing X button Steps to reproduce: 1. Open a document using Minimized and ReadOnly PropertyValues using PowerBuilder OLEObjects. 2. Turn the document visible. 3. Closing the document using the closing X button on Writer. Current behavior: A message appears mentioning a error with the text "Pure Virtual Function call" r6025 Expected behavior: Close the document. Further information: Closing the document using File->Exit works perfectly. Doesn't throw a error like the closing X button. My last OpenOffice installation "OpenOffice.org 3.1.1" didn't had this problem. Operating System: Windows 7 Version: 4.2.2.1 release
Creating a document based on a template using PowerBuilder OLEObjets and closing the resulting document on the X button doesn't give this error.
Installing Java 64bits as suggested on https://bugs.freedesktop.org/show_bug.cgi?id=74385#c7 doesn't solve the problem.
System Info: Java RE 32bits 1.7.0.51 Java RE 64bits 1.7.0.51 Windows 7 Professional 64bits LibreOffice 4.2.2.1
After closing session and logging in again the error appears to be gone. Maybe, after all, installing Java 64bits actually did something.
More info: I configured the Java 64bits on the Advanced Options of LO. But the selected one still is Java 32bits.
I selected the Java 32bits by my choice. It's perfectly possible to select the Java 64bits radio button. Although I'm not sure the effect of being one or the other selected.
My error is back again.... Regarding fdo#69004 i'm not having his issue.
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg The Procdump procedure didn't generate a dump. The pure virtual function call message appears and procdump says that the process has exited (or terminated). Doesn't generate the file. Trying the WinDbg procedure shortly.
Tried the WinDbg procedure but it always fails when attaching to soffice.bin process... See attachment.
Created attachment 96710 [details] WinDbg fails to attach the soffice.bin process
Makrea: here too it could be interesting you test the renaming of LO directory profile.
It is a fresh install of LO. Nevertheless I'll try renaming the profile.
Renaming the profile didn't solved the error. Also having the error on documents opened without being read-only. I say again, the error only happens when closing LibreOffice Writer using X closing button of the window. When doing File -> Exit LibreOffice the error doesn't appear. Something must be done differently between the two!
Thank you Makrea for your feedback. Do you reproduce the crash in these following simple cases? 1) just open Writer and close LO with X button 2) open Writer, type "test", save in an brand new odt file and close LO with X button The goal is to know if it's dependant of using PowerBuilder OleObjects.
>Do you reproduce the crash in these following simple cases? >1) just open Writer and close LO with X button No. >2) open Writer, type "test", save in an brand new odt file and close LO with X button No. >The goal is to know if it's dependant of using PowerBuilder OleObjects. It seems that is dependent when closing through X button. But closing with the normal File->Exit works fine.
Makrea: it seems it depends on closing with X button + powerbuilder tools. I mean, do you reproduce this when closing with X button but without using powerbuilder tools?
>Do you reproduce the crash in these following simple cases? >1) just open Writer and close LO with X button No, the error doesn't happen. >2) open Writer, type "test", save in an brand new odt file and close LO with X button No, the error doesn't happen. >The goal is to know if it's dependant of using PowerBuilder OleObjects. It seems that opening a document with LO writer using code through Powerbuilder is dependent when closing through X button. On this situation the error happens. But opening a document with LO writer using code through Powerbuilder and closing with the normal File->Exit works fine. The error doesn't happen. >Makrea: it seems it depends on closing with X button + powerbuilder tools. Yes, I state that from the beginning of this tracker and I say again. OpenOffice.org 3.1.1 didn't had this error. >I mean, do you reproduce this when closing with X button but without using powerbuilder tools? I already said in the previous post that I don't and I turned that even clearer in this post.
I can't help more here since I don't know Powerbuilder. Certainly someone else may help.
The problem is something that is done differently by LO when closing with the X button!! Don't you find strange that it doesn't show the error when you open a document and close LO writer using File->Exit, but shows the error when closing using the X button?! And I say again: This error didn't exist on several OpenOffice.org releases. >Certainly someone else may help. I hope so!
On the previous post when i say "open" obviously is through Powerbuilder.
Of course it's strange it happens when you use X button and not otherwise. But I think it's more strange it happens only when using Xbutton + Powerbuilder and not when using Xbutton only. To put it even more clearly, I wonder if Powerbuilder might be the problem. But again, since I don't know Powerbuilder, I can't say and so can't help here.
Same code that opens the document: 1- Working fine with OpenOffice.org 3.1.1. 2- Giving issues with LibreOffice 4.2.2.1. (XButton gives error, File->Exit works fine) My conclusion: Something is done differently between Xbutton and File->Exit procedure of LO. Something that didn't happened on OpenOffice.org 3.1.1. Your conclusion: PowerBuilder is the problem. I really don't know why I spent the time writing the bug...
Please read again my previous comment, I don't say Powerbuilder is the pb I said "I wonder if Powerbuilder might be the problem." You can also re read all my previous comments, you'll notice too I never said there was no pb in LO (that's why I didn't put the status of the bug to WFM, NOTABUG or INVALID and let it to UNCONFIRMED) About the behavior difference between OOo and LO, I just wonder if OOo could be more permissive. For example, html errors in websites were (still are?) well managed in IE and not on some other browsers. In this case, the problem encountered in other browsers isn't the other browsers but the html errors. Again, I don't say it's Powerbuilder since I don't know it, I'm just wondering. And again, I prefer letting someone else to take a look to give his/her opinion.
>About the behavior difference between OOo and LO, I just wonder if OOo could be more permissive. So, if you are arguing this then you are arguing that LO's File->Exit procedure is more "permissive" since in LO closing the document this way doesn't give the error. Again, I say, something is different between what is made when clicking XButton to close and the File->Exit!! >Again, I don't say it's Powerbuilder since I don't know it, I'm just wondering. I'm not wondering when I say that something is being done differently between XButton and File->Exit procedure. That's a fact. If it were the same the error would appear at both procedures or didn't appear at all. >And again, I prefer letting someone else to take a look to give his/her opinion. That's a good idea.
Another fact, it works without using Powerbuilder. Now I'll stop to argue here because it doesn't worth it.
By the lack of response I assume that you agree that File->Exit is more "permissive", (using your words). >Another fact, it works without using Powerbuilder. True. But if you don't care about this issue then you don't care about LO API that can be used by other applications. Newsflash: LO isn't used just in GUI mode!!! >Now I'll stop to argue here because it doesn't worth it. I agree. It's clear you don't care about the issue. I hope another person could help with this. And if another person read this and wants to help the previous comments have all the information.
Created attachment 97398 [details] ProcDump using XButton opened document through API Command used: procdump soffice.bin -e -t
Created attachment 97399 [details] Procdump using File-Exit (document opened through API) command: procdump soffice.bin -e -t Only the exceptions that are thrown by File->Exit are in this dump. I say this because by just opening the File menu several exceptions appear. See other attachments
Created attachment 97400 [details] Procdump Xbutton document opened using GUI Procdump shows exceptions using X Button when using GUI.
Created attachment 97401 [details] Procdump File Exit several exceptions Just opening the File menu throws several exceptions before closing the document.
Created attachment 97402 [details] Exceptions that Procdump lists
Created attachment 97403 [details] Exceptions that are thrown by opening File menu
There has just been a report of a similar (virtual call) error in this forum thread: http://en.libreofficeforum.org/node/9160 In this case it appears to be a clash between the MS Windows 8 anti-malware service and Base (when trying to exit Base). I have solicited further details to clarify if this is the same issue (or not). I realise this report is mainly following a PowerTools line of enquiry, but it may be worth confirming whether this Windows service is (not) a factor also.
>There has just been a report of a similar (virtual call) error in this forum >thread: > >http://en.libreofficeforum.org/node/9160 I looked into it and created a post there with a question to the thread OP. >I realise this report is mainly following a PowerTools line of enquiry, but it >may be worth confirming whether this Windows service is (not) a factor also. I'll look into it but I'm almost certain that it isn't the cause because the error was showing on a XP machine also, where such windows anti-malware services didn't exist. I'll test this issue on the 4.3 LO version to see if the bug is still there. I think it will be there because I followed the Release notes of the launched versions and didn't saw this FDO there and besides this would be closed by someone if it was solved. Anyway, thanks for showing interest on the issue. Anything you would require to track this thing down just ask.
Makrea, I'm the guy who reported the bug on the forum. If there is something I can test to help with this let me know.
Hi Daniel Sank, since your error isn't exactly obtained on the same conditions as this FDO I'll keep the analysis of your issue on your forum thread. Anyway feel free to submit a bug on the LibreOffice bug tracker with your issue.
The error doesn't show up on LO 4.3.2.2! See image attached comparing the procdump execeptions that are thrown on 4.2.2.1 vs 4.3.2.2 using X Button.
Created attachment 107060 [details] Procdump exceptions comparison on 4.2.2.1 vs 4.3.2.2 Procdump exceptions comparison on 4.2.2.1 vs 4.3.2.2
What I see is that the last 406D1388 exception is substituted by two C0000005 Exceptions. Somehow this makes a difference. Unfortunately the procdump version is different but maybe that doesn’t matter. If you want the procdump on the same version I think I could get the version that I used back then.
(In reply to Makrea from comment #37) > The error doesn't show up on LO 4.3.2.2! So the bug can be closed?
I guess you can close the bug. I'll open another if the issue occurs again.
(In reply to Makrea from comment #41) > I guess you can close the bug. > I'll open another if the issue occurs again. Closing as worksforme