Terminal won't accept commands
0
I can't enter any commands into my terminal. If I type something in and hit enter it just moves to the next line but noting happens. This message also shows up after like 10 seconds everytime I open terminal.
-bash(16772,0x7fffe4e2a3c0) malloc: *** mach_vm_map(size=18446744072117301248) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
-bash: xrealloc: cannot allocate 18446744072117299336 bytes
[Process completed]
mac terminal
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
|
show 6 more comments
0
I can't enter any commands into my terminal. If I type something in and hit enter it just moves to the next line but noting happens. This message also shows up after like 10 seconds everytime I open terminal.
-bash(16772,0x7fffe4e2a3c0) malloc: *** mach_vm_map(size=18446744072117301248) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
-bash: xrealloc: cannot allocate 18446744072117299336 bytes
[Process completed]
mac terminal
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
You could always upgrade your machine to 18 exabytes of RAM, so the memory allocation (malloc) won't fail :) Seems like there is a bug in yourbashsomehow. Try changing your shell to something else and see if that avoids the problem. Then you can manually startbashand try to recreate the problem.
– mtak
Sep 29 '17 at 20:24
Does the problem persist across reboots?
– Spiff
Sep 29 '17 at 23:24
This might also be caused by something in one of the bash init files in your home folder (any of .bashrc, .bash_profile, .bash_login, and .profile). Note that these files' names start with ".", and hence are usually invisible. You can look for them in TextEdit, by getting an Open dialog (Command-O), navigating to your home folder (Command-Shift-H), then switching on show invisibles mode (Command-Shift-Period). You can also open the files in TextEdit to view their contents, but be careful about making changes -- TextEdit sometimes uses characters that doesn't work in shell scripts.
– Gordon Davisson
Sep 30 '17 at 0:29
@spiff yes it does
– Tyler Bloom
Sep 30 '17 at 20:56
@GordonDavisson Those files are huge, how would I know if something is wrong in them?
– Tyler Bloom
Oct 2 '17 at 19:30
|
show 6 more comments
0
0
0
I can't enter any commands into my terminal. If I type something in and hit enter it just moves to the next line but noting happens. This message also shows up after like 10 seconds everytime I open terminal.
-bash(16772,0x7fffe4e2a3c0) malloc: *** mach_vm_map(size=18446744072117301248) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
-bash: xrealloc: cannot allocate 18446744072117299336 bytes
[Process completed]
mac terminal
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
I can't enter any commands into my terminal. If I type something in and hit enter it just moves to the next line but noting happens. This message also shows up after like 10 seconds everytime I open terminal.
-bash(16772,0x7fffe4e2a3c0) malloc: *** mach_vm_map(size=18446744072117301248) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
-bash: xrealloc: cannot allocate 18446744072117299336 bytes
[Process completed]
mac terminal
mac terminal
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
asked Sep 29 '17 at 20:04
Tyler BloomTyler Bloom
513
513
You could always upgrade your machine to 18 exabytes of RAM, so the memory allocation (malloc) won't fail :) Seems like there is a bug in yourbashsomehow. Try changing your shell to something else and see if that avoids the problem. Then you can manually startbashand try to recreate the problem.
– mtak
Sep 29 '17 at 20:24
Does the problem persist across reboots?
– Spiff
Sep 29 '17 at 23:24
This might also be caused by something in one of the bash init files in your home folder (any of .bashrc, .bash_profile, .bash_login, and .profile). Note that these files' names start with ".", and hence are usually invisible. You can look for them in TextEdit, by getting an Open dialog (Command-O), navigating to your home folder (Command-Shift-H), then switching on show invisibles mode (Command-Shift-Period). You can also open the files in TextEdit to view their contents, but be careful about making changes -- TextEdit sometimes uses characters that doesn't work in shell scripts.
– Gordon Davisson
Sep 30 '17 at 0:29
@spiff yes it does
– Tyler Bloom
Sep 30 '17 at 20:56
@GordonDavisson Those files are huge, how would I know if something is wrong in them?
– Tyler Bloom
Oct 2 '17 at 19:30
|
show 6 more comments
You could always upgrade your machine to 18 exabytes of RAM, so the memory allocation (malloc) won't fail :) Seems like there is a bug in yourbashsomehow. Try changing your shell to something else and see if that avoids the problem. Then you can manually startbashand try to recreate the problem.
– mtak
Sep 29 '17 at 20:24
Does the problem persist across reboots?
– Spiff
Sep 29 '17 at 23:24
This might also be caused by something in one of the bash init files in your home folder (any of .bashrc, .bash_profile, .bash_login, and .profile). Note that these files' names start with ".", and hence are usually invisible. You can look for them in TextEdit, by getting an Open dialog (Command-O), navigating to your home folder (Command-Shift-H), then switching on show invisibles mode (Command-Shift-Period). You can also open the files in TextEdit to view their contents, but be careful about making changes -- TextEdit sometimes uses characters that doesn't work in shell scripts.
– Gordon Davisson
Sep 30 '17 at 0:29
@spiff yes it does
– Tyler Bloom
Sep 30 '17 at 20:56
@GordonDavisson Those files are huge, how would I know if something is wrong in them?
– Tyler Bloom
Oct 2 '17 at 19:30
You could always upgrade your machine to 18 exabytes of RAM, so the memory allocation (
malloc) won't fail :) Seems like there is a bug in your bash somehow. Try changing your shell to something else and see if that avoids the problem. Then you can manually start bash and try to recreate the problem.– mtak
Sep 29 '17 at 20:24
You could always upgrade your machine to 18 exabytes of RAM, so the memory allocation (
malloc) won't fail :) Seems like there is a bug in your bash somehow. Try changing your shell to something else and see if that avoids the problem. Then you can manually start bash and try to recreate the problem.– mtak
Sep 29 '17 at 20:24
Does the problem persist across reboots?
– Spiff
Sep 29 '17 at 23:24
Does the problem persist across reboots?
– Spiff
Sep 29 '17 at 23:24
This might also be caused by something in one of the bash init files in your home folder (any of .bashrc, .bash_profile, .bash_login, and .profile). Note that these files' names start with ".", and hence are usually invisible. You can look for them in TextEdit, by getting an Open dialog (Command-O), navigating to your home folder (Command-Shift-H), then switching on show invisibles mode (Command-Shift-Period). You can also open the files in TextEdit to view their contents, but be careful about making changes -- TextEdit sometimes uses characters that doesn't work in shell scripts.
– Gordon Davisson
Sep 30 '17 at 0:29
This might also be caused by something in one of the bash init files in your home folder (any of .bashrc, .bash_profile, .bash_login, and .profile). Note that these files' names start with ".", and hence are usually invisible. You can look for them in TextEdit, by getting an Open dialog (Command-O), navigating to your home folder (Command-Shift-H), then switching on show invisibles mode (Command-Shift-Period). You can also open the files in TextEdit to view their contents, but be careful about making changes -- TextEdit sometimes uses characters that doesn't work in shell scripts.
– Gordon Davisson
Sep 30 '17 at 0:29
@spiff yes it does
– Tyler Bloom
Sep 30 '17 at 20:56
@spiff yes it does
– Tyler Bloom
Sep 30 '17 at 20:56
@GordonDavisson Those files are huge, how would I know if something is wrong in them?
– Tyler Bloom
Oct 2 '17 at 19:30
@GordonDavisson Those files are huge, how would I know if something is wrong in them?
– Tyler Bloom
Oct 2 '17 at 19:30
|
show 6 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1254911%2fterminal-wont-accept-commands%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- 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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1254911%2fterminal-wont-accept-commands%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
You could always upgrade your machine to 18 exabytes of RAM, so the memory allocation (
malloc) won't fail :) Seems like there is a bug in yourbashsomehow. Try changing your shell to something else and see if that avoids the problem. Then you can manually startbashand try to recreate the problem.– mtak
Sep 29 '17 at 20:24
Does the problem persist across reboots?
– Spiff
Sep 29 '17 at 23:24
This might also be caused by something in one of the bash init files in your home folder (any of .bashrc, .bash_profile, .bash_login, and .profile). Note that these files' names start with ".", and hence are usually invisible. You can look for them in TextEdit, by getting an Open dialog (Command-O), navigating to your home folder (Command-Shift-H), then switching on show invisibles mode (Command-Shift-Period). You can also open the files in TextEdit to view their contents, but be careful about making changes -- TextEdit sometimes uses characters that doesn't work in shell scripts.
– Gordon Davisson
Sep 30 '17 at 0:29
@spiff yes it does
– Tyler Bloom
Sep 30 '17 at 20:56
@GordonDavisson Those files are huge, how would I know if something is wrong in them?
– Tyler Bloom
Oct 2 '17 at 19:30