Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1605165 - Memory usage destroy my Fedora!!!
Summary: Memory usage destroy my Fedora!!!
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-07-20 10:47 UTC by Mars
Modified: 2018-07-20 10:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Mars 2018-07-20 10:47:12 UTC
# Description of problem:

I use blender FLATPAK for video editing, and i lose lot of memory. It's normal, but end of memory, Fedora is going to uncontrollable!!! I cant stop Blender for my screen, mouse, keyboard and everything is freezed. Blender Continuous eating my memory and i cant stop this... I cant switch other TTY....

I set lower memory usage of Blender, but it should not have been so...


I use magic-sysrq + rei
and i restart gdm with systemctl.

# How reproducible:
Open Flatpak Blender and use all available memory.

Steps to Reproduce:
1. use Flatpak version of blender
2. try to editing video
3. use all memory

# Actual results:
Lost control of fedora. I cant switch to other TTY-s....
I want to use magic-sysrq (And fedora default sysrq is not "1" )

# Expected results:
Out of memory, the Blender (or the system) go swapping, BUT KEYBOARD controll stay in memory to switching other tty or idk... 

# Additional info:

 - Fedora 28
 - Intel i5 5200U
 - ~15GB of RAM
 - 500GB hdd
 - 10GB swap (used ~ 500MB under this event )
 - nvidia 920M 2GB with nouveau ( system show intel broadwell :,( )

Note You need to log in before you can comment on or make changes to this bug.