04-10-2021, 01:49 PM
(04-09-2021, 04:27 PM)TheOldPresbyope Wrote: @cirrower
Thanks for that, Joaquin. lt looks like the two issues are closely related.
I've got some things I have to do IRL before I can return to the HDMI local display issue. In the meantime, if you are willing could you try the following?
1. Install the lsof utility
Code:sudo apt-get -y install lsof
2. When you experience the INVALID_CMDLINE_URL result code, run the following from the command line and report the result
Code:lsof | cut -d' ' -f1 | sort | uniq -c | grep chrom
Here's example output from a moOde 7.1.0 player with local display enabled on an official 7-in LCD display (DSI, not HDMI). The player is behaving normally.
Code:pi@710LD:~ $ lsof | cut -d' ' -f1 | sort | uniq -c | grep chrom
17048 chromium-
In a nutshell, this compound command counts all the open file handles "owned" by any of the chromium browser threads. The number reported above is already outrageously high but nowhere near the limit (set elsewhere). I'm curious to see if you get an even higher count.
Regards,
Kent
Here it is, the first one it's just after installation, two more during idle time, and the last after crashing:
Code:
pi@moode:~ $ lsof | cut -d' ' -f1 | sort | uniq -c | grep chrom
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/default
Output information may be incomplete.
18736 chromium-
pi@moode:~ $ lsof | cut -d' ' -f1 | sort | uniq -c | grep chrom
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/default
Output information may be incomplete.
18571 chromium-
pi@moode:~ $ lsof | cut -d' ' -f1 | sort | uniq -c | grep chrom
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/default
Output information may be incomplete.
18530 chromium-
pi@moode:~ $ lsof | cut -d' ' -f1 | sort | uniq -c | grep chrom
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/default
Output information may be incomplete.
16462 chromium-