VSCode: Way to see what extensions are doing what?
I have a simple TypeScript project I'm working on. I have a bunch of extensions running and everything works great. There's one file in particular, though, that when I edit I get all sorts of weirdness that happens. Intellisense takes forever to load, syntax highlighting goes funky, discovered problems refresh sporadically. I've tried removing/disabling a ton of extensions trying to find the culprit, but so far no luck.
Is there a "Task Manager" view for extensions? A way to see what extensions are active at any point in time or which have been running for a long time? Right now, I'm just shooting in the dark. But if I could see that an extension was taking a long time or something, I might be able to track down the problem.
Thanks!
vscode
asked Feb 9 at 18:52
AaronAaron
63
add a comment |
I have a simple TypeScript project I'm working on. I have a bunch of extensions running and everything works great. There's one file in particular, though, that when I edit I get all sorts of weirdness that happens. Intellisense takes forever to load, syntax highlighting goes funky, discovered problems refresh sporadically. I've tried removing/disabling a ton of extensions trying to find the culprit, but so far no luck.
Is there a "Task Manager" view for extensions? A way to see what extensions are active at any point in time or which have been running for a long time? Right now, I'm just shooting in the dark. But if I could see that an extension was taking a long time or something, I might be able to track down the problem.
Thanks!
vscode
asked Feb 9 at 18:52
AaronAaron
63
add a comment |
I have a simple TypeScript project I'm working on. I have a bunch of extensions running and everything works great. There's one file in particular, though, that when I edit I get all sorts of weirdness that happens. Intellisense takes forever to load, syntax highlighting goes funky, discovered problems refresh sporadically. I've tried removing/disabling a ton of extensions trying to find the culprit, but so far no luck.
Is there a "Task Manager" view for extensions? A way to see what extensions are active at any point in time or which have been running for a long time? Right now, I'm just shooting in the dark. But if I could see that an extension was taking a long time or something, I might be able to track down the problem.
Thanks!
vscode
asked Feb 9 at 18:52
AaronAaron
63
I have a simple TypeScript project I'm working on. I have a bunch of extensions running and everything works great. There's one file in particular, though, that when I edit I get all sorts of weirdness that happens. Intellisense takes forever to load, syntax highlighting goes funky, discovered problems refresh sporadically. I've tried removing/disabling a ton of extensions trying to find the culprit, but so far no luck.
Is there a "Task Manager" view for extensions? A way to see what extensions are active at any point in time or which have been running for a long time? Right now, I'm just shooting in the dark. But if I could see that an extension was taking a long time or something, I might be able to track down the problem.
Thanks!
vscode
vscode
asked Feb 9 at 18:52
AaronAaron
63
asked Feb 9 at 18:52
AaronAaron
63
asked Feb 9 at 18:52
AaronAaron
63
asked Feb 9 at 18:52
AaronAaron
63
asked Feb 9 at 18:52
AaronAaron
63
63
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I don't think that such a utility exists.
Extensions execute in the context of VS Code itself, so their individual execution
is hard to distinguish.
If you know how to cause the problem, to locate the problematic extension
just repeat the action on that file, while each time disabling some more
extensions, until you find the one causing the problem.
See the Microsoft article
Extension Marketplace
for how to list the extensions, disable and re-enable.
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two differenttslintextensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.
– Aaron
Feb 9 at 20:07
add a comment |
There is indeed a method for profiling extensions. It's not as pretty as the Windows Task Manager, but it's something.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions
My problem ended up being a GitHub extension.
answered Feb 9 at 21:33
AaronAaron
63
add a comment |
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
});
}
});
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%2f1403949%2fvscode-way-to-see-what-extensions-are-doing-what%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
I don't think that such a utility exists.
Extensions execute in the context of VS Code itself, so their individual execution
is hard to distinguish.
If you know how to cause the problem, to locate the problematic extension
just repeat the action on that file, while each time disabling some more
extensions, until you find the one causing the problem.
See the Microsoft article
Extension Marketplace
for how to list the extensions, disable and re-enable.
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two differenttslintextensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.
– Aaron
Feb 9 at 20:07
add a comment |
I don't think that such a utility exists.
Extensions execute in the context of VS Code itself, so their individual execution
is hard to distinguish.
If you know how to cause the problem, to locate the problematic extension
just repeat the action on that file, while each time disabling some more
extensions, until you find the one causing the problem.
See the Microsoft article
Extension Marketplace
for how to list the extensions, disable and re-enable.
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two differenttslintextensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.
– Aaron
Feb 9 at 20:07
add a comment |
I don't think that such a utility exists.
Extensions execute in the context of VS Code itself, so their individual execution
is hard to distinguish.
If you know how to cause the problem, to locate the problematic extension
just repeat the action on that file, while each time disabling some more
extensions, until you find the one causing the problem.
See the Microsoft article
Extension Marketplace
for how to list the extensions, disable and re-enable.
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
I don't think that such a utility exists.
Extensions execute in the context of VS Code itself, so their individual execution
is hard to distinguish.
If you know how to cause the problem, to locate the problematic extension
just repeat the action on that file, while each time disabling some more
extensions, until you find the one causing the problem.
See the Microsoft article
Extension Marketplace
for how to list the extensions, disable and re-enable.
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
answered Feb 9 at 19:13
harrymcharrymc
261k14271577
261k14271577
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two differenttslintextensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.
– Aaron
Feb 9 at 20:07
add a comment |
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two differenttslintextensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.
– Aaron
Feb 9 at 20:07
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two different
tslint extensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.– Aaron
Feb 9 at 20:07
The hard part is replicating the problem. By reviewing the @installed list yet again, I did finally see I had two different
tslint extensions running, and uninstalling one seems to have fixed the problem. Ugh. Time to look at the vscode code and see if there's something I can contribute! :) Thanks for your time.– Aaron
Feb 9 at 20:07
add a comment |
There is indeed a method for profiling extensions. It's not as pretty as the Windows Task Manager, but it's something.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions
My problem ended up being a GitHub extension.
answered Feb 9 at 21:33
AaronAaron
63
add a comment |
There is indeed a method for profiling extensions. It's not as pretty as the Windows Task Manager, but it's something.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions
My problem ended up being a GitHub extension.
answered Feb 9 at 21:33
AaronAaron
63
add a comment |
There is indeed a method for profiling extensions. It's not as pretty as the Windows Task Manager, but it's something.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions
My problem ended up being a GitHub extension.
answered Feb 9 at 21:33
AaronAaron
63
There is indeed a method for profiling extensions. It's not as pretty as the Windows Task Manager, but it's something.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions
My problem ended up being a GitHub extension.
answered Feb 9 at 21:33
AaronAaron
63
edited Feb 9 at 22:11
answered Feb 9 at 21:33
AaronAaron
63
answered Feb 9 at 21:33
AaronAaron
63
answered Feb 9 at 21:33
AaronAaron
63
63
add a comment |
add a comment |
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.
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%2f1403949%2fvscode-way-to-see-what-extensions-are-doing-what%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
