Am 20.10.21 um 00:01 schrieb Larry Len Rainey:
I have posted in the forum for help but have not gotten anything that helped - I would love to find a way to see why. I know this is not the right way but I hope someone has an idea why and or how to find the problem and fix it.
First of all, does it consume CPU in those 30 seconds or not? * If it does, you could try some profiling with "perf". (From the package of the same name.) So run e.g. "perf record vlc", then close VLC after it has started. Then run "perf report" to get an idea where the most time is spent. * More likely it doesn't and instead waits. That's a bit more difficult but not insurmountable. Install bcc-tools and kernel-devel, then run "sudo /usr/share/bcc/tools/offcputime -p $PID", where $PID is the pid of the relevant process. (The script might be slow to start. If that's the case, run without "-p $PID" and instead filter the stacks after the fact for vlc or whatever program you're running.) Then paste the results here, just the top symbols for perf or the bottom results for offcputime (the longest waits come last) or open a bug right away if you think you know the culprit. In fact opening a bug report isn't the worst idea, even if you don't have any idea what component is at fault. Possibly it's some mutexes though, i.e. user space waiting for user space, which could get a bit harder. Best regards, Aaron