apport should become controllable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
As a developer I'm not very satisfied with the current behavior of apport. After an abort trap in an application in development (a Scheme kernel with reference counting) apport silently brings the machine down trying to "analyze" my software in development (you can be glad it's open source anyway) to tell me after some time there wouldn't be enough memory to analyze the problem and "send a report to the developers". Well, that is me right now but when you implement a new memory management scheme you do stress tests. That software in development sets it's own stack and virtual address space limits and just aborts when there is no more memory available. Some parts are making heavy use of the call stack and even gdb takes a lot of time to "analyze" all those frames - but only on explicit request. But apport tries the same without any limits on the process it seems and that way it pushes "all the desktop" into the swap area.
As a developer I would like apport to become controllable instead of automatically creating problems after what seemed to be a simple crash of some yet unknown application.
According to your guidelines my system is unsupported because of missing updates (you call that a "freeze") so please don't send me any questions.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CrashReports:
640:1000:
640:1000:
640:0:
640:1000:
CurrentDesktop: Unity
Date: Sun Sep 20 10:53:41 2015
InstallationDate: Installed on 2015-06-08 (103 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitec
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.