High memory usage from “git status -z -u”?












4














I am running Ubuntu 16.04. Recently I often find one or two "git status -z -u" process that each takes more than 5GB of memory. So I try to figure out what's going wrong. pstree gives me some output like this:



systemd──lightdm──lightdm──upstart──2*[git]


Apparently upstart started these git processes. So I try to list all jobs of upstart



$ initctl list

indicator-application start/running, process 2364

unicast-local-avahi stop/waiting

update-notifier-crash stop/waiting

upstart-udev-bridge start/running, process 1773

update-notifier-hp-firmware stop/waiting

xsession-init stop/waiting

dbus start/running, process 1774

no-pinentry-gnome3 stop/waiting

update-notifier-cds stop/waiting

gnome-keyring-ssh stop/waiting

gnome-session (Unity) start/running, process 2007

ssh-agent stop/waiting

unity7 start/running, process 2132

upstart-dbus-session-bridge start/running, process 1812

gpg-agent start/running

indicator-messages start/running, process 2343

logrotate stop/waiting

indicator-bluetooth start/running, process 2344

unity-panel-service start/running, process 2009

hud start/running, process 1969

im-config start/running

unity-gtk-module stop/waiting

session-migration stop/waiting

upstart-dbus-system-bridge start/running, process 1811

at-spi2-registryd start/running, process 1999

indicator-power start/running, process 2345

update-notifier-release stop/waiting

indicator-datetime start/running, process 2346

indicator-keyboard start/running, process 2347

unity-settings-daemon start/running, process 1971

indicator-sound start/running, process 2348

upstart-file-bridge start/running, process 1817

bamfdaemon start/running, process 1828

gnome-keyring stop/waiting

window-stack-bridge start/running, process 1786

indicator-printers start/running, process 2349

re-exec stop/waiting

upstart-event-bridge stop/waiting

unity-panel-service-lockscreen stop/waiting

indicator-session start/running, process 2350


and also



$ initctl status

unity7 start/running, process 2132


I didn't see anything that related to these git processes. Can anyone give me some hints of what's going wrong and how should I locate my problem?
Thanks.






ubuntu memory git







share|improve this question






















  • Is it a really large git project?
    – Philip Kirkbride
    Dec 1 '17 at 16:34






  • 2




    What are the full parameters of the git commands? Also, from the git-status manual - "-u [...] Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree". If these are being run on a large directory tree or on a tree with unexpected mounts to other filesystems, that might be why they are taking unexpectedly large piles of time and resources.
    – DopeGhoti
    Dec 1 '17 at 16:37










  • @DopeGhoti Just git status -z -u. The problem is that I don't know which process called git status.
    – Qin Heyang
    Dec 2 '17 at 11:24
















4














I am running Ubuntu 16.04. Recently I often find one or two "git status -z -u" process that each takes more than 5GB of memory. So I try to figure out what's going wrong. pstree gives me some output like this:



systemd──lightdm──lightdm──upstart──2*[git]


Apparently upstart started these git processes. So I try to list all jobs of upstart



$ initctl list

indicator-application start/running, process 2364

unicast-local-avahi stop/waiting

update-notifier-crash stop/waiting

upstart-udev-bridge start/running, process 1773

update-notifier-hp-firmware stop/waiting

xsession-init stop/waiting

dbus start/running, process 1774

no-pinentry-gnome3 stop/waiting

update-notifier-cds stop/waiting

gnome-keyring-ssh stop/waiting

gnome-session (Unity) start/running, process 2007

ssh-agent stop/waiting

unity7 start/running, process 2132

upstart-dbus-session-bridge start/running, process 1812

gpg-agent start/running

indicator-messages start/running, process 2343

logrotate stop/waiting

indicator-bluetooth start/running, process 2344

unity-panel-service start/running, process 2009

hud start/running, process 1969

im-config start/running

unity-gtk-module stop/waiting

session-migration stop/waiting

upstart-dbus-system-bridge start/running, process 1811

at-spi2-registryd start/running, process 1999

indicator-power start/running, process 2345

update-notifier-release stop/waiting

indicator-datetime start/running, process 2346

indicator-keyboard start/running, process 2347

unity-settings-daemon start/running, process 1971

indicator-sound start/running, process 2348

upstart-file-bridge start/running, process 1817

bamfdaemon start/running, process 1828

gnome-keyring stop/waiting

window-stack-bridge start/running, process 1786

indicator-printers start/running, process 2349

re-exec stop/waiting

upstart-event-bridge stop/waiting

unity-panel-service-lockscreen stop/waiting

indicator-session start/running, process 2350


and also



$ initctl status

unity7 start/running, process 2132


I didn't see anything that related to these git processes. Can anyone give me some hints of what's going wrong and how should I locate my problem?
Thanks.






ubuntu memory git







share|improve this question






















  • Is it a really large git project?
    – Philip Kirkbride
    Dec 1 '17 at 16:34






  • 2




    What are the full parameters of the git commands? Also, from the git-status manual - "-u [...] Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree". If these are being run on a large directory tree or on a tree with unexpected mounts to other filesystems, that might be why they are taking unexpectedly large piles of time and resources.
    – DopeGhoti
    Dec 1 '17 at 16:37










  • @DopeGhoti Just git status -z -u. The problem is that I don't know which process called git status.
    – Qin Heyang
    Dec 2 '17 at 11:24














4












4








4







I am running Ubuntu 16.04. Recently I often find one or two "git status -z -u" process that each takes more than 5GB of memory. So I try to figure out what's going wrong. pstree gives me some output like this:



systemd──lightdm──lightdm──upstart──2*[git]


Apparently upstart started these git processes. So I try to list all jobs of upstart



$ initctl list

indicator-application start/running, process 2364

unicast-local-avahi stop/waiting

update-notifier-crash stop/waiting

upstart-udev-bridge start/running, process 1773

update-notifier-hp-firmware stop/waiting

xsession-init stop/waiting

dbus start/running, process 1774

no-pinentry-gnome3 stop/waiting

update-notifier-cds stop/waiting

gnome-keyring-ssh stop/waiting

gnome-session (Unity) start/running, process 2007

ssh-agent stop/waiting

unity7 start/running, process 2132

upstart-dbus-session-bridge start/running, process 1812

gpg-agent start/running

indicator-messages start/running, process 2343

logrotate stop/waiting

indicator-bluetooth start/running, process 2344

unity-panel-service start/running, process 2009

hud start/running, process 1969

im-config start/running

unity-gtk-module stop/waiting

session-migration stop/waiting

upstart-dbus-system-bridge start/running, process 1811

at-spi2-registryd start/running, process 1999

indicator-power start/running, process 2345

update-notifier-release stop/waiting

indicator-datetime start/running, process 2346

indicator-keyboard start/running, process 2347

unity-settings-daemon start/running, process 1971

indicator-sound start/running, process 2348

upstart-file-bridge start/running, process 1817

bamfdaemon start/running, process 1828

gnome-keyring stop/waiting

window-stack-bridge start/running, process 1786

indicator-printers start/running, process 2349

re-exec stop/waiting

upstart-event-bridge stop/waiting

unity-panel-service-lockscreen stop/waiting

indicator-session start/running, process 2350


and also



$ initctl status

unity7 start/running, process 2132


I didn't see anything that related to these git processes. Can anyone give me some hints of what's going wrong and how should I locate my problem?
Thanks.






ubuntu memory git







share|improve this question













I am running Ubuntu 16.04. Recently I often find one or two "git status -z -u" process that each takes more than 5GB of memory. So I try to figure out what's going wrong. pstree gives me some output like this:



systemd──lightdm──lightdm──upstart──2*[git]


Apparently upstart started these git processes. So I try to list all jobs of upstart



$ initctl list

indicator-application start/running, process 2364

unicast-local-avahi stop/waiting

update-notifier-crash stop/waiting

upstart-udev-bridge start/running, process 1773

update-notifier-hp-firmware stop/waiting

xsession-init stop/waiting

dbus start/running, process 1774

no-pinentry-gnome3 stop/waiting

update-notifier-cds stop/waiting

gnome-keyring-ssh stop/waiting

gnome-session (Unity) start/running, process 2007

ssh-agent stop/waiting

unity7 start/running, process 2132

upstart-dbus-session-bridge start/running, process 1812

gpg-agent start/running

indicator-messages start/running, process 2343

logrotate stop/waiting

indicator-bluetooth start/running, process 2344

unity-panel-service start/running, process 2009

hud start/running, process 1969

im-config start/running

unity-gtk-module stop/waiting

session-migration stop/waiting

upstart-dbus-system-bridge start/running, process 1811

at-spi2-registryd start/running, process 1999

indicator-power start/running, process 2345

update-notifier-release stop/waiting

indicator-datetime start/running, process 2346

indicator-keyboard start/running, process 2347

unity-settings-daemon start/running, process 1971

indicator-sound start/running, process 2348

upstart-file-bridge start/running, process 1817

bamfdaemon start/running, process 1828

gnome-keyring stop/waiting

window-stack-bridge start/running, process 1786

indicator-printers start/running, process 2349

re-exec stop/waiting

upstart-event-bridge stop/waiting

unity-panel-service-lockscreen stop/waiting

indicator-session start/running, process 2350


and also



$ initctl status

unity7 start/running, process 2132


I didn't see anything that related to these git processes. Can anyone give me some hints of what's going wrong and how should I locate my problem?
Thanks.






ubuntu memory git




ubuntu memory git






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 1 '17 at 16:31









Qin HeyangQin Heyang

212




212












  • Is it a really large git project?
    – Philip Kirkbride
    Dec 1 '17 at 16:34






  • 2




    What are the full parameters of the git commands? Also, from the git-status manual - "-u [...] Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree". If these are being run on a large directory tree or on a tree with unexpected mounts to other filesystems, that might be why they are taking unexpectedly large piles of time and resources.
    – DopeGhoti
    Dec 1 '17 at 16:37










  • @DopeGhoti Just git status -z -u. The problem is that I don't know which process called git status.
    – Qin Heyang
    Dec 2 '17 at 11:24


















  • Is it a really large git project?
    – Philip Kirkbride
    Dec 1 '17 at 16:34






  • 2




    What are the full parameters of the git commands? Also, from the git-status manual - "-u [...] Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree". If these are being run on a large directory tree or on a tree with unexpected mounts to other filesystems, that might be why they are taking unexpectedly large piles of time and resources.
    – DopeGhoti
    Dec 1 '17 at 16:37










  • @DopeGhoti Just git status -z -u. The problem is that I don't know which process called git status.
    – Qin Heyang
    Dec 2 '17 at 11:24
















Is it a really large git project?
– Philip Kirkbride
Dec 1 '17 at 16:34




Is it a really large git project?
– Philip Kirkbride
Dec 1 '17 at 16:34




2




2




What are the full parameters of the git commands? Also, from the git-status manual - "-u [...] Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree". If these are being run on a large directory tree or on a tree with unexpected mounts to other filesystems, that might be why they are taking unexpectedly large piles of time and resources.
– DopeGhoti
Dec 1 '17 at 16:37




What are the full parameters of the git commands? Also, from the git-status manual - "-u [...] Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree". If these are being run on a large directory tree or on a tree with unexpected mounts to other filesystems, that might be why they are taking unexpectedly large piles of time and resources.
– DopeGhoti
Dec 1 '17 at 16:37












@DopeGhoti Just git status -z -u. The problem is that I don't know which process called git status.
– Qin Heyang
Dec 2 '17 at 11:24




@DopeGhoti Just git status -z -u. The problem is that I don't know which process called git status.
– Qin Heyang
Dec 2 '17 at 11:24










1 Answer
1






active

oldest

votes


















0














@DopeGhoti is correct in the comments. In my case, it turns out to be the problem of Visual Studio Code working on dictionary from mounted network locations. After disable the git in Visual Studio Code, the problem is gone.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f408229%2fhigh-memory-usage-from-git-status-z-u%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    @DopeGhoti is correct in the comments. In my case, it turns out to be the problem of Visual Studio Code working on dictionary from mounted network locations. After disable the git in Visual Studio Code, the problem is gone.






    share|improve this answer


























      0














      @DopeGhoti is correct in the comments. In my case, it turns out to be the problem of Visual Studio Code working on dictionary from mounted network locations. After disable the git in Visual Studio Code, the problem is gone.






      share|improve this answer
























        0












        0








        0






        @DopeGhoti is correct in the comments. In my case, it turns out to be the problem of Visual Studio Code working on dictionary from mounted network locations. After disable the git in Visual Studio Code, the problem is gone.






        share|improve this answer












        @DopeGhoti is correct in the comments. In my case, it turns out to be the problem of Visual Studio Code working on dictionary from mounted network locations. After disable the git in Visual Studio Code, the problem is gone.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 22 hours ago









        Qin HeyangQin Heyang

        212




        212






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2funix.stackexchange.com%2fquestions%2f408229%2fhigh-memory-usage-from-git-status-z-u%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

            How to make a Squid Proxy server?

            Image
            1 I want to set up squid proxy server for monitoring user activity in a network and Internet Web URL filtering for user. I also want to configure the user login, user log, user access group, and block unwanted web sites in my network. Please help me and guide me the full process to do this. server proxy squid share | improve this question edited Jul 31 '12 at 14:45 Jorge Castro 37.1k 107 422 617 asked Jul 31 '12 at 5:16 Goivind Tiwari Goivind Tiwari ...
            Read more

            Is this a new Fibonacci Identity?

            Image
            6 1 $begingroup$ I have found the following Fibonacci Identity (and proved it). If $F_n$ denotes the nth Fibonacci Number, we have the following identity begin{equation} F_{n-r+h}F_{n+k+g+1} - F_{n-r+g}F_{n+k+h+1} = (-1)^{n+r+h+1} F_{g-h}F_{k+r+1} end{equation} where $F_1 = F_2 = 1$ , $r leq n$ , $h leq g$ , and $n, g, k in mathbb{N}$ . It is not too hard to show that this identity subsumes Cassini's Identity, Catalan's Identity, Vajda's Idenity, and d'Ocagne's identity to name a few. I have done a pretty thorough literature review, and I have not found anything like this, but I am still wondering if anyone has seen this identity before? I found this by accident after noticing some patterns in some analysis work I was doing, so if this is already known I would be curious to see w...
            Read more

            19世紀

            Image
            この記事は検証可能な参考文献や出典が全く示されていないか、不十分です。 出典を追加して記事の信頼性向上にご協力ください。 （ 2012年3月 ） 千年紀: 2千年紀 世紀: 18世紀 - 19世紀 - 20世紀 十年紀: 1800年代 1810年代 1820年代 1830年代 1840年代 1850年代 1860年代 1870年代 1880年代 1890年代 19世紀に君臨した大英帝国。 19世紀 （じゅうきゅうせいき）は、西暦1801年から西暦1900年までの100年間を指す世紀。 目次 1 19世紀の歴史 1.1 国民国家の成立 1.2 帝国主義の興隆 1.3 列強の植民地争奪戦 2 できごと 2.1 1800年代 2.2 1810年代 2.3 1820年代 2.4 1830年代 2.5 1840年代 2.6 1850年代 2.7 1860年代 2.8 1870年代 2.9 1880年代 2.10 1890年代 2.11 1900年代 3 文化 3.1 文学 3.2 音楽 3.3 思想 3.4 科学 3.5 技術 4 人物 4.1 ヨーロッパ 4.1.1 政治家・王族 4.1.1.1 フランス 4.1.1.2 オーストリア＝ハンガリー 4.1.1.3 ロシア 4.1.1.4 イギリス 4.1.1.5 ドイツ（プロイセンほかドイツ領邦を含む） 4.1.1.6 北欧 4.1.1.7 イタリア 4.1.1.8 スペイン 4.1.1.9 ベルギー 4.1.1.10 ギリシア 4.1.2 軍人 4.1.3 実業家 4.1.4 科学と技術 4.1.5 思想と哲学・人文諸学 4.1.6 宗教 4.1.7 文学 4.1.8 美術 4.1.9 音楽 4.1.10 社会事業家 4.1.11 探検家・旅行家 4.1.12 料...
            Read more