Mitigation for gvfs memory leak?












5















I have a workflow like this: I fire up my Win7 virtual machine, connect my smartphone, and run Samsung Smartswitch. This worked great in 14.04 LTS.



In 18.04 LTS...not so much. There's a giant memory leak in gvfsd-mtp that hoovers up all 12G of my RAM and brings my system to a halt.



There are bugs related to this and I've reported another. My question is, can there be any mitigation for this? Is there a way to fence in gvfs so it cannot use up all the RAM?










share|improve this question























  • I have the same issue. Any news?

    – Madh
    Jun 17 '18 at 13:31






  • 1





    New kernel on 18.04 did not help. Neither did a workaround I found on superuser to limit memory use by process :(

    – Organic Marble
    Jun 17 '18 at 14:15






  • 1





    In my case I can stop gvfsd-mtp process (pkill -STOP gvfsd-mtp) to avoid the memory increase.

    – Madh
    Jun 17 '18 at 14:57











  • Thanks. As I was writing this I realized I was probably doing the workaround wrong - I was limiting virtualbox and it should have been gvfs. I won't be able to try it again for a few days

    – Organic Marble
    Jun 17 '18 at 18:22











  • I confirm the issue.

    – markroxor
    Jul 5 '18 at 10:48
















5















I have a workflow like this: I fire up my Win7 virtual machine, connect my smartphone, and run Samsung Smartswitch. This worked great in 14.04 LTS.



In 18.04 LTS...not so much. There's a giant memory leak in gvfsd-mtp that hoovers up all 12G of my RAM and brings my system to a halt.



There are bugs related to this and I've reported another. My question is, can there be any mitigation for this? Is there a way to fence in gvfs so it cannot use up all the RAM?










share|improve this question























  • I have the same issue. Any news?

    – Madh
    Jun 17 '18 at 13:31






  • 1





    New kernel on 18.04 did not help. Neither did a workaround I found on superuser to limit memory use by process :(

    – Organic Marble
    Jun 17 '18 at 14:15






  • 1





    In my case I can stop gvfsd-mtp process (pkill -STOP gvfsd-mtp) to avoid the memory increase.

    – Madh
    Jun 17 '18 at 14:57











  • Thanks. As I was writing this I realized I was probably doing the workaround wrong - I was limiting virtualbox and it should have been gvfs. I won't be able to try it again for a few days

    – Organic Marble
    Jun 17 '18 at 18:22











  • I confirm the issue.

    – markroxor
    Jul 5 '18 at 10:48














5












5








5


2






I have a workflow like this: I fire up my Win7 virtual machine, connect my smartphone, and run Samsung Smartswitch. This worked great in 14.04 LTS.



In 18.04 LTS...not so much. There's a giant memory leak in gvfsd-mtp that hoovers up all 12G of my RAM and brings my system to a halt.



There are bugs related to this and I've reported another. My question is, can there be any mitigation for this? Is there a way to fence in gvfs so it cannot use up all the RAM?










share|improve this question














I have a workflow like this: I fire up my Win7 virtual machine, connect my smartphone, and run Samsung Smartswitch. This worked great in 14.04 LTS.



In 18.04 LTS...not so much. There's a giant memory leak in gvfsd-mtp that hoovers up all 12G of my RAM and brings my system to a halt.



There are bugs related to this and I've reported another. My question is, can there be any mitigation for this? Is there a way to fence in gvfs so it cannot use up all the RAM?







18.04 gvfs memory-leak






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 15 '18 at 17:48









Organic MarbleOrganic Marble

10.9k63358




10.9k63358













  • I have the same issue. Any news?

    – Madh
    Jun 17 '18 at 13:31






  • 1





    New kernel on 18.04 did not help. Neither did a workaround I found on superuser to limit memory use by process :(

    – Organic Marble
    Jun 17 '18 at 14:15






  • 1





    In my case I can stop gvfsd-mtp process (pkill -STOP gvfsd-mtp) to avoid the memory increase.

    – Madh
    Jun 17 '18 at 14:57











  • Thanks. As I was writing this I realized I was probably doing the workaround wrong - I was limiting virtualbox and it should have been gvfs. I won't be able to try it again for a few days

    – Organic Marble
    Jun 17 '18 at 18:22











  • I confirm the issue.

    – markroxor
    Jul 5 '18 at 10:48



















  • I have the same issue. Any news?

    – Madh
    Jun 17 '18 at 13:31






  • 1





    New kernel on 18.04 did not help. Neither did a workaround I found on superuser to limit memory use by process :(

    – Organic Marble
    Jun 17 '18 at 14:15






  • 1





    In my case I can stop gvfsd-mtp process (pkill -STOP gvfsd-mtp) to avoid the memory increase.

    – Madh
    Jun 17 '18 at 14:57











  • Thanks. As I was writing this I realized I was probably doing the workaround wrong - I was limiting virtualbox and it should have been gvfs. I won't be able to try it again for a few days

    – Organic Marble
    Jun 17 '18 at 18:22











  • I confirm the issue.

    – markroxor
    Jul 5 '18 at 10:48

















I have the same issue. Any news?

– Madh
Jun 17 '18 at 13:31





I have the same issue. Any news?

– Madh
Jun 17 '18 at 13:31




1




1





New kernel on 18.04 did not help. Neither did a workaround I found on superuser to limit memory use by process :(

– Organic Marble
Jun 17 '18 at 14:15





New kernel on 18.04 did not help. Neither did a workaround I found on superuser to limit memory use by process :(

– Organic Marble
Jun 17 '18 at 14:15




1




1





In my case I can stop gvfsd-mtp process (pkill -STOP gvfsd-mtp) to avoid the memory increase.

– Madh
Jun 17 '18 at 14:57





In my case I can stop gvfsd-mtp process (pkill -STOP gvfsd-mtp) to avoid the memory increase.

– Madh
Jun 17 '18 at 14:57













Thanks. As I was writing this I realized I was probably doing the workaround wrong - I was limiting virtualbox and it should have been gvfs. I won't be able to try it again for a few days

– Organic Marble
Jun 17 '18 at 18:22





Thanks. As I was writing this I realized I was probably doing the workaround wrong - I was limiting virtualbox and it should have been gvfs. I won't be able to try it again for a few days

– Organic Marble
Jun 17 '18 at 18:22













I confirm the issue.

– markroxor
Jul 5 '18 at 10:48





I confirm the issue.

– markroxor
Jul 5 '18 at 10:48










2 Answers
2






active

oldest

votes


















2














You can stop gvfsd-mtp process to avoid the memory increase:



pkill -STOP gvfsd-mtp





share|improve this answer































    2














    It should be solved in upcoming release of gvfs (version 1.39.90, if I understand the version scheme). The fixing commit is this.



    I had the same bug but with gvfsd-google, as I use GDrive as storage for Déjà Dup Backup.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036636%2fmitigation-for-gvfs-memory-leak%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      You can stop gvfsd-mtp process to avoid the memory increase:



      pkill -STOP gvfsd-mtp





      share|improve this answer




























        2














        You can stop gvfsd-mtp process to avoid the memory increase:



        pkill -STOP gvfsd-mtp





        share|improve this answer


























          2












          2








          2







          You can stop gvfsd-mtp process to avoid the memory increase:



          pkill -STOP gvfsd-mtp





          share|improve this answer













          You can stop gvfsd-mtp process to avoid the memory increase:



          pkill -STOP gvfsd-mtp






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 5 '18 at 16:58









          MadhMadh

          1364




          1364

























              2














              It should be solved in upcoming release of gvfs (version 1.39.90, if I understand the version scheme). The fixing commit is this.



              I had the same bug but with gvfsd-google, as I use GDrive as storage for Déjà Dup Backup.






              share|improve this answer




























                2














                It should be solved in upcoming release of gvfs (version 1.39.90, if I understand the version scheme). The fixing commit is this.



                I had the same bug but with gvfsd-google, as I use GDrive as storage for Déjà Dup Backup.






                share|improve this answer


























                  2












                  2








                  2







                  It should be solved in upcoming release of gvfs (version 1.39.90, if I understand the version scheme). The fixing commit is this.



                  I had the same bug but with gvfsd-google, as I use GDrive as storage for Déjà Dup Backup.






                  share|improve this answer













                  It should be solved in upcoming release of gvfs (version 1.39.90, if I understand the version scheme). The fixing commit is this.



                  I had the same bug but with gvfsd-google, as I use GDrive as storage for Déjà Dup Backup.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 14 at 12:58









                  Bender250Bender250

                  211




                  211






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036636%2fmitigation-for-gvfs-memory-leak%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                      Mangá

                      Eduardo VII do Reino Unido