While it's totally true that malicious code might be embedded in anything
(especially ms formats... but we won't talk about this :)), I doubt it
would trigger a reaction as bad as a reboot, especially under recent OS.
Crashing a user program is very unlikely to cause a system reboot, except
if it call some regular reboot code, that would trigger a "clean" reboot,
windows closing and stuff. Most likely output is simply the program
crashing/getting in an unstable state.
As I said, it's not completely ruling out the possibility of a catastrophic
crash caused by some code issue, but it's fearly reasonnable to suppose
that loading this file make LO expand to use more memory than usual,
touching a faulty area. If the computer usually work without issue, maybe
the ppt file is very large, or very complex, or the LO loading routine
doesn't handle it nicely and cause the memory cost to increase.
It would be interesting to know wether the reboot is "hard" (instant black
screen) or soft (windows closing down normally).
Also, if the ppt file isn't sensitive, it would be useful to put it on some
kind of file sharing site for people to try loading it.
2013/7/21 Andrew Brown <firstname.lastname@example.org>
My two cents worth would rather be to focus on the actual Powerpoint data
file that is the source of the problem, when attempted to being opened. If
it has any corruption in it, or possibly a piece of malware made to
disguise and represent itself as a Powerpoint presentation, then I would
accept it crashing and forcing a reboot of the PC, especially if there is
no malware protection in place, on a Windows system especially. Virus
writers can easily embed bad and malicious code into documents,
presentations and spreadsheets.
Try another known working presentation data file, and see if this also
causes the crash with LO and the PC, if not, then you know where your
source of your problem is.
On 21/07/2013 05:20 PM, Gabriel Risterucci wrote:
There is not much stuff (if any) in LO that could cause a reboot of a
computer. Although it's not possible to completely rule out a LO issue,
suggest you run some memory testing program (like memtest86+), as it's
more likely that your issue is related to faulty memory/hardware.
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy