Whole system lock-up because of crashing application

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Hi,

this is still an issue for me.

When using no swap partition, this could be related to
Ubuntu Bug #159356, or to the following kernel bug:
http://groups.google.com/group/linux.kernel/browse_thread/thread/910c08e97eb0357e

But I still have the problem when using a swap partition. The system
becomes extremely unresponsive, i.e. processes are influenced which
don't even wait for harddisk i/o. Even the mouse pointer stalls when the
swap area is used. Using cryptographic swap (via the kernel-based
dm-crypt) further worsens the situation.

I've written a small C++ utility that allocates memory to simulate the
behaviour of an application requesting memory.

This file can be compiled with
"g++ memory_overcommit.cc -o memory_overcommit.bin" and run with
"./memory_overcommit.bin".

You could run a tool like "top" in another shell to watch the memory
usage and eventually terminate the process.

Updated version to avoid segfault when system behaves correctly.

I have this, too. Also, the above lines of code seem to reproduce the lock-up of my whole system.

I would say this shouldn't happen. I can confirm this.

I want to add, that this is not related to Adobe Reader.

Ulrich Lukas, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]