Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IAR Build Utility starts automatically and uses 100% processor #48

Closed
JanWielgus opened this issue May 12, 2023 · 4 comments
Closed

IAR Build Utility starts automatically and uses 100% processor #48

JanWielgus opened this issue May 12, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@JanWielgus
Copy link

I have a problem with the newest version (v1.20.3). When I open the IAR project in VS Code and click on the IAR icon on the left panel, in about 10 seconds this extension opens ~30 IAR Build Utility processes out of nowhere, that uses in total 100% of the processor. I waited for about 30 minutes, but nothing happens and PC is barely usable.
In Task Manager it looks like this:
image

I have IAR Embedded Workbench 8.3
Everything works on version 1.20.2 and 1.20.1 (those versions I tested)

Thank you for your help!

@jlonnberg
Copy link
Collaborator

@JanWielgus Can you please describe your project structure, e.g., number of .ewp files in the opened folder, number of configurations and number of files in the project? I suspect that this is part of the system that handles underlying information which basically runs a series to builds to gather enough information, so if the folder contains many ewp-files and/or projects with many files we might have a problem there.

@jlonnberg jlonnberg self-assigned this May 12, 2023
@jlonnberg jlonnberg added the bug Something isn't working label May 12, 2023
@JanWielgus
Copy link
Author

@jlonnberg In opened folder I have indeed about 200 .ewp files, each of them have at least two configurations and many have four. Many projects are quite big.
Can something be done with this?

@HampusAdolfsson
Copy link
Collaborator

Hi, I just answered someone else with the same problem in another issue. See my reply here:
#49 (comment)

@jlonnberg
Copy link
Collaborator

Closing as duplicate of #49

@jlonnberg jlonnberg closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants