I save a file in Eclipse CDT, do a build, run the program and go back to editing. Then Eclipse grabs the CPU for some 3 - 5 seconds completely, producing an irritating delay in keyboard latency. after some 2, 3 minutes the same issue shows up.
Eclipse Indigo is running on Debian Squeeze inside of a VirtualBox which may use 6 out of 8 processors of a iCore7 8-hyperthread machine. Interesting enough, on the host OS, I see all 8 hyperthreads busy.
This is getting annoying since after every build it stops me 5 seconds from continuing my work. It looks liek it is connected with the indexer, since turnign off the indexer removes the problem (but then the IDE is a btit useless).
I have ample of memory for eclipse, for the Debian guest and for the Java VM.
Any ideas what I can do?
UPDATE: The problem is now solved. I am running
* A fresh version of Debian
* A fresh version of Eclipse
* Without virtualization, ie. on pure metal
* Booted natively from Debian from an SSD
Do not know what the reason was, but the problem is gone now.
Related
I'm working with source code of Unreal Engine 4.27.2. A lot of time I built an engine at my old Windows 11(I don't remeber a version), that I set up with a lot of any Tweaks. Everything was good: I had a full CPU load(100%, 180Watt) while building a project and got a built project for 30-40min.
But for some reason, I reinstall my windows to more new ones. It was Windows 11 too. And from this moment I have trouble with the building of the Engine. It can load my CPU for 100%. I have reinstalled about 10 different Windows 10\11, different versions, different variations of all. I tried to use a lot of usually-for-me Tweaks, settings, etc. But nothing can't load the CPU for 100% while building.
What I tried to do:
Setup a Power Options to Ultra\Maximum
Disable the default windows defender
Disable default any spy utils using regedit and policies-editor
Set high priority for cl.exe\MSBuild.exe\link.exe using Regedit(didn't work out, didn't set)
Make 4th point using .bat commands with infinity loop(where I set high priority for cl\MSBuild\link). It became a bit better.
Tried to make env-var CL with value /MP
Tried to kill any other processes
Tried to set the highest performance for my CPU using tools of my ASUS Motherboard.
I'm sure that I did many other things, but I don't remember.
Now I use Windows 10 LTSC 21H2 19044.1381(installed 6 hours ago) and the project building for 5 hours and 20%\50Watt loading of CPU!!!
I tried to resolve it for more than one week! Help, please :(
I will be very grateful for any help!
PS: my PC:
i7 12700k
64Gb RAM(DDR4)
Samsung 980Pro and 970 Evo Plus(tried to build on both of them)
Also I use MSVC 19
I found an issue.
The problem was bound to my OS settings. For some reason, all apps had 'below normal' priority in the Task Manager, so my compiler didn't want to load my CPU over ~20%.
I resolved that using Bill2's Process Manager and set minimum priority for all processes 'normal'. Instead of 5 hours of build, I got 25min.
I work on c++ project on VS, and a lot of operations that were fast now super slow. Saving a file could take minutes, intelISense may take forever to show hints, navigating functions takes long time. I tried to reinstall VS 2017, but behavior havent changed. I tried to move to VS 2019, but observe same things. I have 6700k, 32gb ram, Windows 10 with latest updates, both VS installed on NVME M2 drive(around 3000 mb/s write/read), so my PC rather fast. Any ideas how I can solve it? Development sometimes feels unbearable.
EDIT: So, I deleted everything that was remotely close to Visual Studio (VS15-17-19, build tools, Nsight, CUDA integration) and installed clean VS19 installation only with v142 tools for C++. So far(few hours in) it works fine. I dont know what was the problem, but I hope it fixed it. Will report later if lags will return.
I am trying to boot up a saved am using Macbook pro with M1 chip.
I tried the steps given at this answer. But was not able to boot up the VM. Can someone confirm this problem or already found out a solution to it?
I got the error "The virtual machine 'Ubuntu 20.04 64bit 1' has terminated unexpectedly during startup with exit code 1 (0x1)." below:
Had the same issue on Mac OS Big Sur 11.4 when I was trying to add my Ubuntu instance (on Intel tho), nothing suggested here and other topics helped.
Turned out you have to give access (Full Disc Access) to Virtual Box in Settings. Go to Settings -> Security & Privacy -> Privacy -> Full Disc Access -> plus sign (unlock it if needed) -> choose Virtual Box Application -> Open.
After that I was able to choose my Ubuntu image in Finder.
<New user, reputation too low to comment on David's post!>
As per David Leitko's answer, VirtualBox is an x86 (more specifically, AMD64/x86_64) virtualization hypervisor. However, it appears from various discussions I've seen on this topic that many users don't really understand what this really means.
So, it means not only that VirtualBox only runs on x86 CPUs, but also that it requires all the other elements of the x86 platform. These include system memory, various bus controllers (PCI, USB), hard disk controllers, sound cards, graphics, BIOS/UEFI, etc. None of these take the same form on the Apple Silicon platform - i.e. they don't use any of the standards built up in the PC ecosystem over the last 40 years.
So, not only will VirtualBox not work on Apple Silicon, it will never work on Apple Silicon. There will never be any way to run a VirtualBox image that ran on an Intel Mac on an Apple Silicon Mac. Ever.
The canonical discussion thread on the VirtualBox forums that covers this in more detail is here.
VirtualBox is an x86 virtualization hypervisor. It only runs on an x86 platform. See https://www.virtualbox.org
While Rosetta 2 will run many x86 apps very well on an M1 Mac, virtualization products are not supported per this Apple document
I just had the exact same problem after updating my VirtualBox app on MacOS Big Sur. What worked for me was to go to System Preferences - Security & Privacy - General, and then click the Allow button to allow extensions by Oracle (first click the lock symbol in the lower left of the screen and enter your password).
Actually, during installation I got this pop-up window telling me to do this, but I wasn't quite sure what exactly it wanted me to do. Only after getting this error I took the trouble of looking closer, ahem...
Hope this will fix your problem too!
Environment
I'm using Visual Studio 2019 version 16.7.2 on a Windows 10 VM, hosted by Parallels on a brand new MacBook Pro. The VM has eight virtual processors and sixteen gigs of RAM.
Nothing other than Visual Studio is installed on the VM.
What I'm trying to do
I'm trying to compile a Visual Studio solution consisting of seventeen projects. The projects are relatively small. They're all C# console applications or DLL libraries targeting .NET Core 3.1.
Problem
Typically a Rebuild Solution executed after a Clean Solution takes place in about ten seconds. A typical Build Solution (Ctl-Shft-B) that I execute throughout the day takes place almost instantaneously.
But occasionally, in maybe one build out of five, building the solution/projects causes VBCSCompiler.exe to consume 99% CPU usage and freeze up for approximately thirty to forty-five seconds prior to executing the build. Once it starts executing the build though, everything completes normally. This long delay which occurs time and time again is making my development cycle terribly frustrating. I'd like to find a way to eliminate this delay.
What's Changed
The build executed fine on my Amazon Web Server Windows 2016 m4.xlarge VM. I recently switched over to the Parallels VM to save money. That's when the problem began.
Again, I want to reiterate that the Parallels VM is clean. Nothing other than Visual Studio is installed there.
What I've Tried
The following tactics were applied to no avail.
(1) I turned off the Defender real-time virus checker.
(2) Based on the information in this post, I went to Tools | Options | Nuget Package Manager | General, and unchecked 'Allow Nuget to download missing packages' and 'Automatically check for missing packages'
(3) In Tools | Options | Projects and Solutions | Build and Run, I set the maximum number of parallel projects builds to one.
(4) Based on an answer to an unrelated question, I learned that I can view more information about the build process by setting 'MS Build project build output verbosity' to Detailed. I did so. I waited for the freeze to occur so I could examine the last line of output prior to the freeze. It reads as follows:
Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn
This line always appears immediately before a freeze.
(5) Based on the output above, I Googled 'shared compilation' and discovered this post.
As a hobbyist programmer, the discussion that took place there, as well as the link in the accepted answer is well above my pay grade. It's unintelligible to me. If the answer lives in that post, I can't decipher it.
Any ideas on how to solve this intermittent freeze? If I can't figure it out, I'll have to assume it's something about my Parallels Windows 10 VM that's causing the problem, and revert back to developing on an Amazon server. I'd prefer to avoid that if possible because of the added expense.
Thanks for your consideration.
Best,
Festus
I'm VERY new to CLion so please be gentle :)
I took a project I did for a programming course I'm taking, I managed to build it, but when I tried to run it the CLion just freezes. I tried to run it in debug mode, but no success there either - it waits for a few seconds and then I recieve a message: "command timed out".
I thought the problem might be in my program, so I wrote a simple "Hello World" program - still no success.
few technical specs that might help:
I use CLion 1.2.1 (Newest version).
For my toolchains I use TDM-GCC compiler (downloaded from here: http://tdm-gcc.tdragon.net/download) - I actually do not use the newest version - I use version 4.9.2-3 instead - because I wanted the GDB to be 7.8 so Clion supports it).
My computer runs windows 10 (64 bit), intel core i5-4210U, 8 GB RAM (for what it's worth...)
hope you could help me.
Avast antivirus running … changing its setting as you can find here Stop avast! from attacking my own programs can help...
– nnn