Big mess happens when memory is full. #23476

Closed
opened 2026-01-31 08:43:24 +00:00 by claunia · 3 comments
Owner

Originally created by @0wwafa on GitHub (Jul 26, 2025).

If I have 10-20 shells open and browsers and the memory fills up (you can easily do it using the browser for example)
Then as the screen blanks (browser crashing) when the system recovers some openterminal shells are locked and unresponsive (so losing history and everything)

I understand it's a borderrline case, but it happens all the time.

Image

This is an example. 4 shells are still working but the others don't even show up when clicking on them. I can only close them from the taskbar.

Originally created by @0wwafa on GitHub (Jul 26, 2025). If I have 10-20 shells open and browsers and the memory fills up (you can easily do it using the browser for example) Then as the screen blanks (browser crashing) when the system recovers some openterminal shells are locked and unresponsive (so losing history and everything) I understand it's a borderrline case, but it happens all the time. <img width="1324" height="109" alt="Image" src="https://github.com/user-attachments/assets/b83c05ae-ec37-4abc-9393-7f9e40ceb8c9" /> This is an example. 4 shells are still working but the others don't even show up when clicking on them. I can only close them from the taskbar.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 08:43:25 +00:00
Author
Owner

@lhecker commented on GitHub (Jul 28, 2025):

Handling OOM gracefully in large applications is always a pain, because it has to be designed for that from the ground up. This app isn't. In the meantime, I suggest increasing the size of your swap space.

@lhecker commented on GitHub (Jul 28, 2025): Handling OOM gracefully in large applications is always a pain, because it has to be designed for that from the ground up. This app isn't. In the meantime, I suggest increasing the size of your swap space.
Author
Owner

@DHowett commented on GitHub (Jul 30, 2025):

Thanks for filing. The console host uses somewhere between 0.5 and 11 megabytes of memory in its steady state. We probably shouldn't hang when you run out of memory, we should just crash like everyone else does. 🙂

(We're not likely to invest in fixing this any time soon!)

@DHowett commented on GitHub (Jul 30, 2025): Thanks for filing. The console host uses somewhere between 0.5 and 11 megabytes of memory in its steady state. We probably shouldn't _hang_ when you run out of memory, we should just crash like everyone else does. 🙂 (We're not likely to invest in fixing this any time soon!)
Author
Owner

@0wwafa commented on GitHub (Aug 2, 2025):

Thanks for filing. The console host uses somewhere between 0.5 and 11 megabytes of memory in its steady state. We probably shouldn't hang when you run out of memory, we should just crash like everyone else does. 🙂

(We're not likely to invest in fixing this any time soon!)

How dumb is that? @DHowett
If there is a memory problem at least don't crash and allow to retrieve the history and the backlog AS IT WAS.

@0wwafa commented on GitHub (Aug 2, 2025): > Thanks for filing. The console host uses somewhere between 0.5 and 11 megabytes of memory in its steady state. We probably shouldn't _hang_ when you run out of memory, we should just crash like everyone else does. 🙂 > > (We're not likely to invest in fixing this any time soon!) How dumb is that? @DHowett If there is a memory problem at least don't crash and allow to retrieve the history and the backlog AS IT WAS.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23476