{"thread":{"id":"47866","subject":"Git Stash Creates sh.exe.stackdump (STATUS_STACK_OVERFLOW)","startedAt":"2018-02-16T18:47:15Z","lastAt":"2018-04-28T11:55:21Z","messageCount":2,"participants":["Derek Foulk","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"339567","messageId":"ec9aec59d4d6497a84431f1abeae147d@mail2.colheli.loc","threadId":"47866","inReplyTo":null,"subject":"Git Stash Creates sh.exe.stackdump (STATUS_STACK_OVERFLOW)","fromName":"Derek Foulk","fromEmail":"dfoulk@colheli.com","sentAt":"2018-02-16T18:47:08Z","receivedAt":"2018-02-16T18:47:15Z","isPatch":false,"sender":{"key":"dfoulk@colheli.com","avatar":null},"body":"Hi,\n\nAn issue has arisen sometime between 2.16.1.windows.1 and 2.16.1.windows.4 in Git.\n\nWhen you execute `git stash` commands (stash/pop/apply?), a sh.exe.stackdump file is generated that contains the following:\n\nException: STATUS_STACK_OVERFLOW at rip=7FFB2C324B97\nrax=0000000000000010 rbx=0000000000000000 rcx=0000000000000010\nrdx=000000000000000C rsi=00000000FFFFAAE0 rdi=00007FFB23B8D4F0\nr8 =00000000FFFFAA18 r9 =00000000FFFFAA50 r10=00000000FFFFA000\nr11=00000000FFE03E70 r12=00000000FFFFB500 r13=000000000015C000\nr14=000000000000014C r15=0000000000000000\nrbp=00000000FFFFAA50 rsp=00000000FFFFAA08\nprogram=C:\\Program Files\\Git\\usr\\bin\\sh.exe, pid 41552, thread unknown (0x949C)\ncs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B\nStack trace:\nFrame        Function    Args\n000FFFFAA50  7FFB2C324B97 (00000000104, 000FFFFAAC8, 7FFB2C302178, 00000000000)\n000FFFFAA50  7FFB2C302277 (7FFB23B8D4F0, 7FFB23B8D4F0, 00000000001, 00000230022)\n000FFFFAAC8  7FFB28D1D1F4 (7FFB2C280000, 7FFB2C3021F0, 7FFB2C2EFAE0, 7FFFFFFEFFFF)\n000FFFFAC90  7FFB28D1D071 (9E09000600010000, 365AE1E0F447, 00000000023, 000FFFFADB8)\n000FFFFAC90  7FFB28D1CA44 (7FFB23B8D700, 00000000000, 00000000000, 7FFB23B8D700)\n000FFFFAC90  7FFB23AF03A0 (000FFFFAC90, 000FFFFADB8, 000000F3DF0, 00000091380)\n000FFFFAC90  7FFB23AC37DB (000FFFFB5C0, 00000000000, 000FFFFB970, 000000F3DF0)\n000FFFFB3F9  7FFB23A9E4D0 (00000000002, 000FFFFB7E8, 00000000000, 00180010018)\n00180010018  7FFB23A9CFDD (00000000000, 000FFFFB720, 00000000000, 000FFFFB7C0)\n000FFFFB720  7FFB23A95543 (000FFFFB890, 000000001C8, 00000000000, 00180271780)\n00000000420  7FFB28D1D7F6 (00000000001, 00000000000, 000FFFFB970, 00100000001)\n00000000420  7FFB29C4E4E3 (00000000020, 00000000000, 000FFFFBAF0, 00000000001)\n00000000420  001800AB022 (000FFFFBA90, 00000000000, 00000000000, 00180300748)\n000FFFFBB10  001800ABBD5 (00100410FBB, 00000000000, 0060004DF10, 001004E9740)\n000FFFFBD10  0018011C93B (00100410FBB, 00000000000, 0060004DF10, 001004E9740)\n000FFFFBD10  00002DEE458 (00100410FBB, 00000000000, 0060004DF10, 001004E9740)\nEnd of stack trace (more stack frames may be present)\n\nThe end result is you cannot pop your stashed changes (the .stackdump file injects itself into the stashed changes, then one is created before the pop occurs):\n\nI've confirmed updating to the latest Git causes this to occur on three different workstations (and repositories).\n\nI've tried downgrading to 2.15, but the issue has persisted (it did not exist prior to updating to 2.16).\n\nThanks,\n-Derek\n\nEnvironment:\nWindows 10 (Fall Creators Update)\nGit v2.16.1.windows.4 (Default installation options w/ Added context menu options)\nGit Bash\n"},{"id":"346031","messageId":"nycvar.QRO.7.76.6.1804281353110.79@tvgsbejvaqbjf.bet","threadId":"47866","inReplyTo":"ec9aec59d4d6497a84431f1abeae147d@mail2.colheli.loc","subject":"Re: Git Stash Creates sh.exe.stackdump (STATUS_STACK_OVERFLOW)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2018-04-28T11:55:13Z","receivedAt":"2018-04-28T11:55:21Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Derek,\n\nOn Fri, 16 Feb 2018, Derek Foulk wrote:\n\n> An issue has arisen sometime between 2.16.1.windows.1 and 2.16.1.windows.4 in Git.\n> \n> When you execute `git stash` commands (stash/pop/apply?), a sh.exe.stackdump file is generated that contains the following:\n> \n> Exception: STATUS_STACK_OVERFLOW at rip=7FFB2C324B97\n> rax=0000000000000010 rbx=0000000000000000 rcx=0000000000000010\n> rdx=000000000000000C rsi=00000000FFFFAAE0 rdi=00007FFB23B8D4F0\n> r8 =00000000FFFFAA18 r9 =00000000FFFFAA50 r10=00000000FFFFA000\n> r11=00000000FFE03E70 r12=00000000FFFFB500 r13=000000000015C000\n> r14=000000000000014C r15=0000000000000000\n> rbp=00000000FFFFAA50 rsp=00000000FFFFAA08\n> program=C:\\Program Files\\Git\\usr\\bin\\sh.exe, pid 41552, thread unknown (0x949C)\n> [...]\n\nI saw similar reports on the Git for Windows bug tracker. Probably the\nmost relevant one is this here:\nhttps://github.com/git-for-windows/git/issues/1562\n\nIn essence, the culprit there seems to be an overzealous anti-malware\ncalled Comodo Internet Security. Maybe your setup has the same problem?\n\nCiao,\nJohannes\n"}]}