-
Notifications
You must be signed in to change notification settings - Fork 53
/
Copy path4 GitBash Could not fork child process.html
63 lines (63 loc) · 2.46 KB
/
4 GitBash Could not fork child process.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
<h1>GitBash Error: Could Not Fork Child Process</h1>
<h2>The Problem: </h2>
<h2>Opening a GitBash windows displays an error message "Could not fork child process"</h2>
<p><img src="https://i.stack.imgur.com/Tps5X.png" alt="enter image description here"></p>
<p><br></p>
<h2>The Solution</h2>
<p><strong>Solution 1: </strong>(adapted from: <a
href="https://rotadev.com/git-bash-error-could-not-fork-child-process-there-are-no-available-terminals-1-dev/">https://rotadev.com/git-bash-error-could-not-fork-child-process-there-are-no-available-terminals-1-dev/</a>
)</p>
<ul>
<li>The problem occurs on Windows with Git Bash when the Git Bash console is closed/killed without using ‘exit’.<ul>
<li>1. Close all Git Bash windows.</li>
<li>2. Open Task manager (Keyboard shortcut: Control + Shift + Escape.)</li>
<li>3. Find the ‘Git for Windows’ process.<ul>
<li>If you do not see any "Git for Windows" processes, look for:<ul>
<li>python</li>
<li>msys2</li>
</ul>
</li>
</ul>
</li>
<li>4. Kill any processes that are running that meet the above criterion.</li>
<li>5. Re-open Git Bash. The problem should be fixed.</li>
<li>See the Prevention heading below for how to avoid this error in the future</li>
</ul>
</li>
</ul>
<p><strong>Solution 2 (if #1 did not resolve the issue):</strong></p>
<ul>
<li>The problem may also occur due to VS Code's integrated terminal.</li>
<li>Close any Visual Studio Code windows </li>
<li>Check Task Manager for any Visual Studio Code processes that are still running and kill them.</li>
<li>Re-open Git Bash. The problem should be fixed.</li>
<li>See the Prevention heading below for how to avoid this error in the future</li>
</ul>
<p><strong>Solution 3 (will always work but not convenient)</strong></p>
<ul>
<li>If neither solution worked, restart your computer.</li>
<li>While not convenient, it will solve the issue. See the Prevention heading below for how to avoid this error in
the future.</li>
</ul>
<p><br></p>
<h2>Prevention</h2>
<ul>
<li>Always make sure to shut down jupyter notebook properly before closing. <ul>
<li>From jupyter's file view:<ul>
<li>Click Shutdown on the top right corner</li>
</ul>
</li>
<li>From GitBash:<ul>
<li>Press "Control + C" to quit jupyter server from the GitBash window that started jupyter
notebook.<ul>
<li>If asked y/n, answer "y".</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<p><br></p>
<p></p>
<p><br></p>