You are here

Loading LibreOffice 5.0.1 Crashed My Computer

5 posts / 0 new
Last post
Chim
Offline
Last seen: 1 year 4 months ago
Joined: 2010-10-10 21:35
Loading LibreOffice 5.0.1 Crashed My Computer

I barely upgraded from LibreOffice 5.0.0 Rev 2 to 5.0.1. Now as soon as I attempt to load LibreOffice, my avast 2015 10.4.2233 will bring up 2 Deep Screen Popups to check it out and about 3 seconds later ... POOF! My computer crashes and reboots.

Seeing ONE avast Deep Screen Popup when bringing up Apps is normal, but I had never seen any App cause the appearance of 2 Deep Screen Popups. I think one is checking out LibreOffice.exe and the other one is checking out LibreOffice.bin or something along those lines.

I tried the process again. Again, attempting to bring up LibreOffice 5.0.1 caused my computer to crash. To verify whether the culprit was LibreOffice 5.0.1 or avast, I tried bringing up my old LibreOffice 5.0.0 from my other Flash Drive. That version came up with no problems.

My computer has Windows XP Pro SP3 ... Pentium 4 ... 2 Gig RAM ... avast 2015 10.4.2233.

John T. Haller
John T. Haller's picture
Online
Last seen: 7 min 55 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Working Here

I installed LibreOffice Portable 5.0.1 Multilingual Standard into my Windows XP Pro SP3 virtual machine to C:\LibreOfficePortable as a test. The machine has Avast 2015 10.4.2233 installed with virus definitions 150921-1. The install completed without issue. Right clicking on the LibreOfficePortable folder and selecting to scan with Avast stated No Threats Found. Running LibreOfficePortable.exe brought LibreOffice up as normal without issue.

Have you made any alterations to Avast or to LibreOffice Portable settings-wise? Have you tried a fresh install?

Note that, as always, LibreOffice Portable is 100% clean and safe. And a regular app generally can't crash a Windows OS without something wrong with the OS itself (an existing infection, faulty video card driver, etc).

Sometimes, the impossible can become possible, if you're awesome!

Chim
Offline
Last seen: 1 year 4 months ago
Joined: 2010-10-10 21:35
Third Try ... Same Results

I uninstalled the working LibreOffice 5.0.0 Rev 2 from my Flash Drive and installed 5.0.1 again. As with the previous 2 times, upon trying to bring up LibreOffice 5.0.1, it crashes my computer and causes it to reboot.

As to whether I made any settings changes to LibreOffice? I can't do that because as I mentioned, upon attempting to bring up LibreOffice ... or more specifically --- LibreOffice Writer, it crashes in the middle of avast's Deep Screen scan. So, I don't remotely get anywhere near being able to make any settings changes. Never get to see the UI so as to do anything.

As to my avast? I barely installed the latest version this past Sunday. The settings were the usual, typical settings that I set. Nothing hardcore, nothing remotely advanced. Besides, out of all my Apps that I have on my Hard Drive and on my Flash Drive, only that LibreOffice 5.0.1 (Writer) has freaked out my computer.

My guess is that it's possible that I just have a corrupt setup file for that LibreOffice 5.0.1 even though the install indicates that it went through successfully. I have Dial Up Internet, so I won't immediately be able to download another copy of LibreOffice 5.0.1. I'll have to wait until one of my periodic times that I have access to one of my sisters' computers with High Speed Internet. It'll probably be a newer LibreOffice version by then ... and the problem solved either way. Hopefully anyway.

Gord Caswell
Gord Caswell's picture
Offline
Last seen: 2 hours 55 min ago
DeveloperModerator
Joined: 2008-07-24 18:46
Local install

To ensure this is only happening with the portable build on your machine, can you try installing LibreOffice (non-portable) and see if it has the same problem?

If so, this isn't a portable-specific problem, and should be addressed by contacting LibreOffice's support mechanisms.

If it is only happening with the portable build, we can try to figure out what's happening. However, as noted above, the same behaviour is not seen on as similar system, so we'll likely need more details, such as the exact install path.

Once you've tested a local install, feel free to uninstall it if you wish, this is only for testing purposes.

Chim
Offline
Last seen: 1 year 4 months ago
Joined: 2010-10-10 21:35
More, But Odd and Inconclusive Info

I conducted some more experimentation.

The previous 3 failed LibreOffice 5.0.1 bring up attempts on 2 different installs had been on my E: Flash Drive. The install path - E:\PortableApps\LibreOfficePortable.

So, I got curious and this time installed LibreOffice 5.0.1 on my G: Flash Drive. After this install, I noticed that this time avast did NOT conduct a Deep Screen scan upon my bringing up first LibreOffice 5.0.1 Impress ... followed by Math, Draw, Calc, Base and finally Writer. And interestingly enough, now with there being no avast Deep Screen scans of any of those LibreOffice 5.0.1 programs, they all came up fine without any problems.

I'm guessing that the reason this time around avast did not conduct Deep Screen scans of LibreOffice 5.0.1 is because it had already Whitelisted LibreOffice from when it brought up LibreOffice 5.0.0 Rev 2 without any problems.

So, with my now being able to bring up LibreOffice 5.0.1 on my G: Flash Drive's install, I decided to yet again install LibreOffice 5.0.1 on my original E: Flash Drive for a 3rd time. The verdict? This time around, I WAS able to bring up all the LibreOffice 5.0.1 programs successfully without any problems ... no crash ... no reboot. As with my G: Flash Drive's install ... I noticed that this time avast did NOT conduct a Deep Screen scan when LibreOffice was coming up on my E: Flash Drive's install.

What does this all mean? Well, it's inconclusive, but I guess there's a possibility that the problem could be on avast's end. The bad thing is that for some unknown reason, for 2 or 3 months now, I have not been able to log in into the avast Forums with my Dial Up. I used to be able to in the past, but not now. So I cannot inform avast for them to look into this issue to see if the problem is on their end.

Log in or register to post comments