I have never used phantomJs to do anything, but for some reason it has like 5 processes opened at one time and they take about 90% of my CPU. I can't just uninstall it, because uninstaller is corrupted. I have tried every solution posted on google but nothing works for me :/ Here's screenshot of my Taskmanager http://imgur.com/a/y7N1M
Related
My first stack overflow question, here we go.
Last week the computer on which a prototype vision application written in C#/.net was running crashed due to an unreleated reason. this resulted in the need to fresh install windows (windows 10 IOT). after installing windows, halcon 20.11 progress and setting the licenses the application starts, but no output is shown on the smart window control, even tho this worked beforehand?
i have been trying to debug this problem for the last day, but have had no luck, what i have allready tried:
used the remote debugging toe verify that the image is captured and processed and "displayed".
checked the system logs for any warnings, there were none.
Tried one of the example programs the come with Halcon, which also does **not **work.
Ran the application on my development PC, which worked flawlessly as it always did.
Reinstalling Halcon.
does anyone have had any similar experiences and/or any clue how to solve this problem?
problem has been solved. in the end a reset of the bios settings to there default values did the trick. Don't know what they exact cooperative was, but at least it works once again.
I recently switched out my AMD Ryzen 7 3800x for a Ryzen 9 5950x. I also purchase and M.2.
I got these today and installed them on my computer. I have an SSD, a hard Drive and now an M.2
I deleted Fortnite from my hard drive and then installed it on my M.2 the game started up fine it played okay no problems
Then I uninstalled Call of duty modern warfare. I reinstalled it along with its launcher on the new M.2
After installation I went to start the game and check out how it runs with the new stuff.
My problem is that every time I try to start the game it loads for 10 seconds then my computer reboots. I cannot even load into the game because the computer just reboots itself.
I have tried uninstalling and reinstalling again,
I tried running as Administrator,
I attempted to reset the M.2 and see is that was the issue,
I also uninstalled and reinstalled fortnite and it worked perfectly fine.
Does anyone have any tips on what to check or what to do? Everything is up to date. I also reset my bios just in case my old overclock settings for the old CPU had something to do with the crashing of this new one, but nothing happened it kept crashing.
I also attempted to install call of duty vanguard and call of duty cold war. Same thing happened with those as well. I then installed a free to play game and it also happened with that.
I am not sure where to go from here. If anyone has any tips on how to fix this I would be more than pleased. Thank you so much
I'm having a problem with TensorFlow (CPU) on Ubuntu 14.04 (VM, droplet), where running a script is fast the first time, but when running the same (or another) script directly after completion of the first run, things become very slow.
I'm talking minutes instead of seconds. Even simple test scripts (like those provided in the tutorial) take forever, with no visible CPU load.
For comparison: first run of the test script from the tutorial gives:
{real:0m0.790s, user:0m0.688s, sys:0m0.111s}
Second run of the same script, directly after completion of the first run gives:
{real: 2m46.628s, user: 0m0.783s, sys: 0m0.104s}
Eventually, things seem to clear up and performance is back (only for one run though).
I narrowed the problem down to this:
sess=tf.Session()
takes very long. Apparently resources used by a previous Session are not properly released [?]. My scripts use the Context manager, like
with tf.Session() as sess:
sess.run(...)
My latest hypothesis is that this has to do with system properties (virtual machine settings, hypervisor issues interacting with the context manager of TF). Using the docker container of TF makes no difference. Rebooting didn't help either. The same scripts run OK on OS X.
To make sure it's obvious what happened and that this question is answered: This occurred because tensorflow was reading from /dev/random instead of /dev/urandom. On some systems, /dev/random can exhaust its supply of randomness and block until more is available, causing the slowdown. This has now been fixed in github. The fixes are included in release 0.6.0 and later.
So I have Ubuntu 14.04 Installed on my system with a few "tweaks", mainly ccsm. I also have google chromium browser installed as well. I do a lot of work in the browser and usually have 10+ tabs open in my system.
I also like to use the multi-window (Workspace) and have 8 Workspaces (thus one of the reasons for ccsm).
Once I leave the computer and try to come back (before the screen locks), the computer is COMPLETELY frozen with my HDD running at very high speeds. I have a system monitor that monitors the CPU activity and HD activity and right before those things freezes, my RAM is at 100% and so is my HDD.
I'm wondering if anyone can help me FIGURE OUT what the problem is? I've been using ubuntu since '08 so I'm familiar with it. I just don't know where to start!
HELP!
I can not deal with the problem until I install the following packages as follows
sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal
You could get the detailed reason from http://www.howtoeverything.net/linux/hardware/random-freezes-integrated-hd-4000-graphics
Maybe you have to consider the Google Chrome or Chromium, whose two or more different Flash plugins conflict with each other, and the freeze problem disappear after you Disable the Flash plugins in the webpage opened by inputting
chrome://plugins
in the URL address of Chrome
Or another useful method of changing the chrome plugins is to uninstall the google-chrome completely,and then install the current chrome with newest flash plugin.
After all the above are done, the system need restart.
Hope it can help. Good luck!
Since re-installing Windows 7 Ultimate 64-bit SP1, sometimes processes take a long time to close. This happens most frequently when launching them from VS2010, but it's not limited to that. A common case is a Windows app with a console (/SUBSYSTEM:console) that appears to close correctly, but the console remains open for seconds or minutes. Eventually the "press any key to close" message appears on the console, and the process can be terminated.
How can I diagnose this problem?
I installed Windows 7 Ultimate 64-bit SP1, but this time the vanilla (not N) version
The only driver I manually installed is the NVIDIA display driver, but I've tried multiple WHQL versions
The symptoms closely match the question at
Visual studio debug console sometimes stays open and is impossible to close Even non-console apps are affected, however.
Both native and managed applications suffer from this.
WRONG: I believed only 32-bit processes were affected, but 64-bit ones also suffer.
if a debugger is already attached, and I break while the process is waiting, the debugger
says:
The process appears to be deadlocked (or is not running any
user-mode code). All threads have been stopped.
I can't attach a debugger to a process while its in this state
I can't kill these zombie processes from Task Manager or
ProcessExplorer, even when closing all handles that refer to said
processes. (I can't close lsass.exe's handles, though)
ProcessExplorer says that the hanging function of the only thread
that the each hung process has is ntdll!RtlDosSearchPath_Ustr.
Most of the time I have to close Visual Studio completely to allow
the zombie processes to close.
The last event that Process Monitor sees at the hang in each case is
a Thread Exit, which succeeds, and it looks like the exit takes the
normal amount of time. When the process finally closes, no events
show up.
LiveKd doesn't show anything when I follow the steps outlined at
http://blogs.technet.com/b/markrussinovich/archive/2005/08/17/unkillable-processes.aspx
It seems like a bad driver is the culprit, so I'm going to reinstall Windows soon.