Created attachment 117304 [details] screenshot A few days ago and today again, I have get the attached error after - opened and modified an existing odt - saved again as odt - exported as PDF rewriting the previous file - closed writer what is it?
does it happens just with one single file or with any file? which Windows version do you run?
Did you try to? Step 1. Firstly, close that program which is showing you the runtime error. Simply press “CTRL +ALT+DEL” button open task manager. Step 2. Click Processes tab in that menu and then again click on “Image name”.Then check your program in the list and click on your program and choose “End Process”. Step 3. Then close the task manager and click on start button. Select control panel and choose option for “Uninstalling a program” Under the program selection. You have to uninstall that program which is showing you the error message. Step 4. Again click on start button and type clean “cleanmgr” into the search box and then press Enter button. Step 5. Carefully choose the drive where you have installed your program recently. Check all the options in that list and click OK and then select Delete files. Step 6. After performing the above step carefully, simply restart your system. Step 7. Reinstall your program again in your system and open your program to confirm that runtime error doesn’t appear again on your computer screen. - See more at: http://www.fixerrs.com/2014/05/Fix-runtime-error-r6025.html#sthash.m0cQ7ro2.dpuf
I'm running Win 8.1 x64. The problem happened occasionally after exiting/closing an odt file (the same file), the file closed OK and reopening it is OK. Once closed/stopped LO Writer the error appeared displayed. Not understanding the cause I'll wish to know the possible origin and the explaination of that type of error. Thanks.
can you uplaod the "guilty" file?
(In reply to tommy27 from comment #4) > can you uplaod the "guilty" file? Hello Tommy, at the moment the problem has no more appeared. Unfortunately the file is too private and the problem was occasional and impossible to replicate at will with a generic file. However, the "guilty" is a very simple text, like many others, and the problem occurred twice after closing Writer immediately before having saved the file first as odt, immediately as pdf.
similar bug report here Bug 86553 - "Document Recovery" dialog is up when a new document saved then closing Writer
(In reply to tommy27 from comment #6) > similar bug report here > > Bug 86553 - "Document Recovery" dialog is up when a new document saved then > closing Writer It seems really the same question. Naruhiko Ogasawara says "".. sometimes see "LibreOfficeDev Document Recovery" dialog "" I have never seen this kind of message, but the "Runtime Error" displayed is exactly the same, and appeared exactly after closure of L.O.
For the past few days, upon closure after save, I get a runtime error from "Microsoft Visual C++ Runtime Library": **Runtime Error! Program: C:\Program Files (x86)\LibreOffice 4\program\soffice.bin R6025 - pure virtual function call** Operating System is: Windows 8.1 - English LibreOffice version is: Version: 4.4.5.2 Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Locale: en_US Component is the writer How can this problem be corrected?
I set status to NEW because another user reproduced it and I revert version to 4.4.4.3 please remember every bug report has to indicate earliest version a bug appeared, not latest.
Same error occurred again. It does not happen every time but about 50% of the time. Opened a document, made minor changes, clicked on the X in the upper right to close. Asked if I wanted to save it, I did. Immediately after the window closed the error came up.
Again today. Made a minor change. Clicked 'X' to close. Asked if I wanted to save. Said to save. Immediately after saving the error came up. Note that since the last time I have opened, edited, and saved this file and many others.
Happened again today. Nothing unusual. Updated a file, clicked on the 'X' to clos. Asked to save, said 'Save'. File saved properly and then the error came up
are you still using 4.4.5.2 or 5.0.2.2?
I am still using 4.4.5.2 When I open LibreOffice and click on 'Check for Updates', it spins for quite a while and then tells me that LibreOffice is up to date.
(In reply to tommy27 from comment #13) > are you still using 4.4.5.2 or 5.0.2.2? Hello Tommy, that is an old question. I too am still using 4452 and checking for updates I get I am up to date, but looking at the official infos we see that the release 5 is ready since the end of july. Then, have we to wait the official ask for updating (I think end-of-life november 18,2015)or it is better to update now? Tanks, regards
hi. i faced this error message most of times in my system windows xp proffessional service pack 3 en-us version of libreoffice. no different which type of document i want to open, edit and even read! i use .txt, .rtf and and microsoft office formats .docx and .doc format. when i open the document, edit it and even edit it, when i press alt f4 to close, libreoffice writer crashes and i get this error message about microsoft visual c runtime library runtime error. 6025 pure virtual function call. or something like this. but i installed microsoft visual c 2005, 2008 and 2010 in my system. and i could not understand what is the reason of this error! i get this message between versions 4.3 and 4.3 which i tested. i tested both installed and portable version and the error message is the same. only when i installed version 5.0.2.1 i did not see this error happen again! by the grace of god and efferts of developers of libreoffice. i tested open office last year and it was without this error. but as i mentioned most of times i opened and close documents with alt f4 in libreoffice versions 4.3 and 4,4, this problem was common and always repeated most of time when reading editing documents specially the .rtf files! i faced this error more than 80 percent when i opened document with libreoffice writer but before version 5!
Without step by step procedure or at minimum some example file or a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information) we can't investigate here. So let's put this one to RESOLVED/INSUFFICIENTDATA and if you still reproduce this with last stable LO version (5.1.2), don't hesitate to reopen this tracker and provide more information. Please don't mixup problems, this tracker is about error message "pure virtual function call", not about freeze in Check update process function. 1 bug per bugtracker to keep it not too difficult to manage.
(In reply to Julien Nabet from comment #17) Well, recently I no more received the error, so I think you can close the problem. Note: what about the similar bug 86553, still in NEW status?
(In reply to gmarco from comment #18) > (In reply to Julien Nabet from comment #17) > > Well, recently I no more received the error, so I think you can close the > problem. > Note: what about the similar bug 86553, still in NEW status? The runtime error can easily be fixed by updating the network drivers. Make sure you check the article which will help you out. http://techstuffsarena.com/2019/02/18/windows-resource-protection-could-not-start-the-repair-service/