Bug 142809
Summary: | Openoffice.org, when started as a normal user is able to cause the system to swap uncontrollably, requiring a reboot to resolve. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Xander D Harkness <harkness> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | gajownik, hp, nobody, pfrields, tmraz, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-03 00:44:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xander D Harkness
2004-12-14 12:27:22 UTC
This is a tricky problem. I suspect the system feels unresponsive because of the sheer amounting of swaping that is going on (and laptop hard disks often have low throughput so this would take an age). However until most of the swap is exhausted the OOM killer won't normally come out. To stay responsive you would have had to have had a very twitchy OOM killer or to have not allowed OOo to use so much swap. You could try changing /proc/sys/vm/overcommit_ratio to a lower number like 25 to see whether that halts OOo's growth quicker... This sounds more like an openoffice bug than a kernel bug. You keep asking for memory, the kernel keeps giving it to you (until you run out of swap, or resource limits kick in). However, it's possible that you're seeing some inefficieny of the vm layer. Is the current 2.6.10 update kernel any better ? See also this thread https://www.redhat.com/archives/fedora-devel-list/2005-January/msg01293.html I don't know that it's a kernel bug but I think it's an OS bug that a user app can effectively shut down the OS for hours (or really, indefinitely; you could *nearly* exhaust VM then just keep allocating and freeing random blocks). By "OS bug" I mean we should at least be setting some userspace tunables or providing some sort of watchdog to avoid this problem, if we can possibly think of a way. Imagine a multiuser timeshare system, you wouldn't want any user to be able to do this. And for an individual workstation, you never want an app bug to cause this state. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you. |