impress crashes desktop ! - presentation with big fies

[AndreK]

Binary package hint: openoffice.org

I've tried to make a few presentations with 10-30MB videos and/or some 3MB image files.
These presentations are dangerous to edit., whole resktop crashes randomly while editing.
I have not found anything in logs, where whould I look ?

This seems to happen only in Ubuntu (mine is 8.04)

ProblemType: Bug
Architecture: i386
Date: Mon Apr 28 14:06:28 2008
DistroRelease: Ubuntu 8.04
Package: openoffice.org-core 1:2.4.0-3ubuntu6
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openoffice.org
Uname: Linux 2.6.24-16-generic i686

[Chris Cheney (ccheney)]

You are probably running out of memory depending on how many images/videos you are adding. Do you recall how many you added before it causes the crash?

Thanks,

Chris

[AndreK (andre-k)]

Hi.
I don't think so. -no decent OS would crash whole desktop because low mem.
1GB RAM most free, 1GB swap , presentation, I guess 60MB

The presentation works sometimes perfectly fine, and crashes desktop about half the time.

[Chris Cheney (ccheney)]

Linux does... or at least used to its called the OOM Killer. See http://en.wikipedia.org/wiki/Out_of_memory

[Chris Cheney (ccheney)]

I think I didn't explain well enough. The OOM Killer, when the system is low on memory (if it is still enabled, I don't know), will kill whatever it feels like and in many cases can end up killing needed programs by accident.

[Chris Cheney (ccheney)]

Linux oomkiller probably should be smart enough to kill the offending app using all the memory instead of various other things running. Reassigning to linux.

[Leann Ogasawara (leannogasawara)]

Can you comment if this is still an issue with the more recent Intrepid Ibex 8.10 release which contains a 2.6.27 based kernel. Please let us know your results. Thanks.

[Chris Cheney (ccheney)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!