My problem is as follows.
From time to time, Xorg starts a process with a heavy CPU load (50-100% only for one thread) and animation a little freezes on the screen (for example, letters are displayed with a delay of about 0.5-2 seconds after they are entered using the keyboard or with micro freezes when video playback).
Please help me figure out what this process does and how to fix the problem with the fact that the graphics has a delay due to it.
Below I leave the full display of the command (taken from "top" command):
Xorg -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{efd6b83b-791f-4698-bfmc-7a0badf342c7} -noreset -displayfd 17
I'm using Manjaro (KDE) and this problem has been happening for at least a year despite regular updates.
What I managed to do myself:
If I somewhat restart the graphical shell: press Ctrl+Alt+F2 (displays a terminal) and then return to Ctrl+Alt+F1 (graphics), then the system reports: Desktop effects were restartet due to a graphics reset, sometimes Xorg disappears process (not always).
Sometimes Xorg process disappears on its own
There is a possibility that this may have something to do with Firefox, which is always open.
Additional Information:
There were big problems with graphics from the very beginning of using a laptop with Linux. From time to time I have to restart the graphical shell due to various glitches when using the computer for a long time without restarting (sleep only), say 20 days (for example, some pop-ups are displayed in black with a 50% probability)
Also sometimes plasmashell takes gigabytes of RAM, which leads to a freeze, and is treated only with "killall plasmashell" and restart
Computer: Lenovo Legion Y540
Video card: NVIDIA GeForce GTX 1650 4GB GDDR5
OS: 5.10.161-1-MANJARO (KDE)
Related
I have an electron app that renders to a 1280x720 canvas and is using requestAnimationFrame. The app works perfectly on my machine running, 16GB ram, i7, x64, with a GTX 1080 GPU. When I run the same app on other computers it runs extremely slow. I have tried a surface go, but also my friends computer who is running much new and better hardware than mine and it still runs at a potatoes rate. Any idea what could cause this discrepancy?
I have tried using setInterval to see if there was a difference and there was a minimal difference but the app is still unplayable. I also tried to combine all my modules into a singleton as per their advice and I noticed a slight increase.
It seems to me like power on and off have two different behaviours:
if I shutdown jetson xavier nx through the operating system and after that turns off the power, jetson xavier wont start when I turn the power back on. First I have to remove the powerplug from the device and reinsert it again.
if I just turns off the power and in that way are closing jetson xavier it will restart as soon as I turn the power on again.
While number two works it seems always better to turn off the operating system first but it is a bit odd to remove and reinsert the cable to restart it.
What is the proper way of doing this? Or does number two nothing to worry about? Or am I better off install some kind of on off switch or what is the most easy way of handle this fundamental thing?
It only works in these three scenarios:
cutting the powersupply - the jetson starts when it is back on
shutting down from menu - the jetson starts if I remove and reconnect the powerplug to the jetson
shutting down from menu - the jetson starts if I wait 5-10 minutes before I start the electricity again
I have a BeagleBone Black rev C with kernel 3.8.13-bone50 and Debian OS version 7.5. The problem that I have is that when I connect the external power supply (5 V) and the board is also connected to USB ( for communication with Cloud 9 IDE) it shuts down after almost 5 seconds.
I searched everywhere on Internet for an answer, but nothing. I also displayed the content of the TPS65217 PMIC but nothing. Nothing that could give me an answer why the board is simply shutting down.
Can someone help me?
Some poor quality power supplies might cause the same kind of problem.
Please see below.
http://elinux.org/Beagleboard:BeagleBoneBlack#Improper_Power_Down....All_Revisions
Seems that the board didn't shutdown after changing a bit in TPS65217 PMIC INT register.
I changed the D5 bit from Interrupt Register from 0 to 1, meaning that no interrupt will be issued when power to AC input is applied or removed.
Command used:
i2cset -f -y 0 0x24 0x02 0x20
This is odd behavior but I have been able to reproduce it 100%. I'm currently testing Neo4j 2.0.1 Enterprise on my laptop and desktop machines. Laptop has 8GB RAM i7 4600U and Desktop has 16GB RAM i7 4770k. (Both machines are running Windows 8.1 x64 ENT and the same version of Java (latest as of FEB 19, 2014).
On first boot of each, when I run an expensive (or not so expensive) query, I can see the memory allocation go up (as expected for the cache). When starting the server, initial allocation is around 200-250mb, give or take. After a few expensive queries, it goes up to about 2GB, which is fine, I want this memory allocation. However, I have a batch script that stops the service, clears out the database and restarts the service (to start fresh when testing different development methods).
After 3 or 4 restarts, I noticed that the memory will NEVER climb above 400mb. Processor usage sits around 30-40% during the expensive query, but memory never increases. I will then get Unknown Error messages in the console when running other expensive queries. This is the same query that after a full reboot of the system, would bring the memory usage up to 2GB.
I'm not sure what could be causing this, or if there is a way to make sure that memory usage continues to be allocated, even on service restart. Rebooting a production server doesn't seem like a viable option, unless running in HA.
This seems so basic that people would be screaming about it, searching the web turned up nothing, but I have tested it on several networks and computers. We are having an issue where we use the .local url to access resources it is very slow. If we use the direct IP address we don’t see these delays.
In our stripped down test setup the device and the computer are on the same switch and are the only devices on the switch. The same thing occurs when we are not in this very limited network configuration. Mac OS X Lion on the command line we are getting these results:
With direct ip:
curl 10.101.62.42 0.01s user 0.00s system 18% cpu 0.059 total
With bonjour name:
curl http://xrx0000aac0fefd.local 0.01s user 0.00s system 0% cpu 5.063 total
It is consistently just above 5 seconds per request to resolve. It does not matter which device we try to connect to, the same seems to be occurring in our iPhone app, and is slow with Python scripts. Safari seems to be able to resolve the names quickly.
We could resolve once and then use the IP address but that first request will still be unacceptably slow, and I don’t think this is the way Bonjour is supposed to work.
We are not exactly sure when this started happening but it was not always this way.
Edit: Another data point. On Snow Leopard it is not slow at resolving:
$ time curl http://hp1320.local > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
101 2848 0 2848 0 0 15473 0 --:--:-- --:--:-- --:--:-- 36512
real 0m0.201s
user 0m0.005s
sys 0m0.009s
This is resolved in iOS 5 and Lion 10.7.2. Which is a huge relief. Unfortunate that 4.3 app users will get this slow behavior. Guess it is another reason to upgrade.
Do the hosts you mentioned show up when you browse for them? Enumeration should be pretty quick:
mdns -B _http._tcp
Maybe there's something slowing the name resolution. If you query the IPs with dig it should return the correct address pretty much instantly:
dig A xrx0000aac0fefd.local #224.0.0.251 -p 5353
Failing that try running tcpdump and see if there's a device that's spewing out multicast packets on the network.