Bug 1329161

Summary: liveusb-creator eated more 90% memory after being left alone for a while
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: liveusb-creatorAssignee: Martin Bříza <mbriza>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: bcl, mbriza, pfrields
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:17:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot
none
dmesg
none
journal none

Description lnie 2016-04-21 10:01:59 UTC
Created attachment 1149402 [details]
screenshot

Description of problem:
I inserted a usb stick which turns out is recognizable by the liveusb-creator(have no idea why, maybe because I have mkfs it too many times ?) and chose the workstation option to do the writing,it kept saying " there are no portable devices connected "
I was thinking that maybe the liveusb-creator will take some time to do the recognize,so I happily used another machine to continue my work.Several minutes later,when I found the screen was locked,I tried to login the system to see whether it starts downloading,and it took me almost one minute to login the system.Still that piece of complaint but has eaten more than 90% mem which makes it very hard for me to open other application.I tried to close it by click the button,but failed,"force out"button,still failed. Finally ,I killed  it by using "kill -p pid"   
Version-Release number of selected component (if applicable):

f24-x86_64

liveusb-creator-3.92.1-1.fc24.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Martin Bříza 2016-04-21 10:13:01 UTC
This is just strange.
Are you using non-free graphical drivers?

I have just tried to plug in all seven flash drives I found around my table in the office and will go for a lunch to see how much does the memory usage raise when I'm gone for about an hour. So far it haven't moved by a bit...

Comment 2 Martin Bříza 2016-04-21 12:08:47 UTC
I tried running it while I was gone and took 158MB of RES memory when I went away and now it takes 153MB.
I guess your issue can be caused either by a broken graphical driver or maybe a broken flash drive causing UDisks to send a lot of data over D-Bus.
Can you report back with what driver are you using and a dmesg log, please?

Comment 3 lnie 2016-04-22 05:10:01 UTC
(In reply to Martin Bříza from comment #2)
> I tried running it while I was gone and took 158MB of RES memory when I went
> away and now it takes 153MB.
> I guess your issue can be caused either by a broken graphical driver or
> maybe a broken flash drive causing UDisks to send a lot of data over D-Bus.
> Can you report back with what driver are you using and a dmesg log, please?
It's unlikely  my usb's fault,cause I just reproduce this bug on that desktop without usb inserted,and my usb can be recognized by the virt-manager.My graphical driver is nouveau,which works pretty well from what I can tell.

Comment 4 lnie 2016-04-22 05:11:18 UTC
Created attachment 1149639 [details]
dmesg

Comment 5 Martin Bříza 2016-04-22 15:50:14 UTC
Hmm, I'm starting to run out of ideas. Can you please provide the journal for the time when FMW was running?

Comment 6 lnie 2016-04-25 04:47:17 UTC
Created attachment 1150242 [details]
journal

Comment 8 Fedora End Of Life 2017-07-25 20:35:29 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2017-08-08 14:17:34 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.