Is this behaviour of VLC normal?
I'm on ubuntu 16.04 unity latest updates installed, I have one of the best Asus gaming laptops in the market, VLC is installed but I never use it.
For the last few months, I wasn't able to shut down my PC, every time I try to do so, the fans start spinning so fast and it hangs, so I just press the shut down button, that problem was only on shutdown, not restart I didn't even bother trying to solve the problem.
Today, while I was working, I noticed the fans doing the same thing that they normally do while shutting down. I ran top noticed 2 vlc instances being run under my username consuming like 122% cpu each, although again I don't use vlc, and I'm not using any program that relies on vlc.
I tried to sudo kill <pid> and sudo killall <pid> and sudo killall vlc but still they weren't killed, that never happened to me before. I killed them from Ubuntu resource monitor, they were killed and the shutdown problem was fixed, and everything went back to normal.
Did that happen to anybody before?
16.04 unity vlc process
asked yesterday
LynobLynob
2,590125192
|
show 4 more comments
I'm on ubuntu 16.04 unity latest updates installed, I have one of the best Asus gaming laptops in the market, VLC is installed but I never use it.
For the last few months, I wasn't able to shut down my PC, every time I try to do so, the fans start spinning so fast and it hangs, so I just press the shut down button, that problem was only on shutdown, not restart I didn't even bother trying to solve the problem.
Today, while I was working, I noticed the fans doing the same thing that they normally do while shutting down. I ran top noticed 2 vlc instances being run under my username consuming like 122% cpu each, although again I don't use vlc, and I'm not using any program that relies on vlc.
I tried to sudo kill <pid> and sudo killall <pid> and sudo killall vlc but still they weren't killed, that never happened to me before. I killed them from Ubuntu resource monitor, they were killed and the shutdown problem was fixed, and everything went back to normal.
Did that happen to anybody before?
16.04 unity vlc process
asked yesterday
LynobLynob
2,590125192
Hi, Lynob, I just updated the script in my answer in a way to be compatible with crontab, that by default works with limited number of environment variables... Now, according to my tests, the script works as it is expected.
– pa4080
yesterday
2
If you're interested in finding out why it's happening, you could runps aux | grep " $(echo -n $(pgrep vlc | xargs ps -o ppid | tail -n +2 | tr -d ' ') | sed 's/ / \| /g') "next time it happens. This would find all running instances of VLC, get the parent PIDs for each of them, and then search for the parent PIDs in the output ofps aux. It might help in tracking down the problem.
– anonymoose
yesterday
3
For the record,sudo kill -9 <pid>would probably have worked where justkilldidn't. The-9means "Kill anything that moves, with extreme prejudice, in the most gruesome way possible". Not much can survive it. Without-9, it's more like "Please die? Please, pretty please with a cherry on top?"
– trysis
yesterday
1
@trysis: Be careful withkill -9, it's dangerous. If for example the application has created a temporary file under/var/lock, it won't be removed. Similarly, buffers won't be flushed, database transactions will not be committed, etc. You could end up with corrupt or missing data if anything was being written anywhere. VLC is probably not doing any of those things, but I would recommend trying to understand the problem before assuming.
– Kevin
yesterday
1
BTW, 99% problems I had with VLC hanging and doing other "strange stuff" were due to it trying to use hardware acceleration for video decoding, or using the "wrong" (whatever that may mean) video backend; I'd try to fiddle with that stuff (disable HW acceleration for codecs, try to change video output backend) and see if anything good comes from it.
– Matteo Italia
yesterday
|
show 4 more comments
I'm on ubuntu 16.04 unity latest updates installed, I have one of the best Asus gaming laptops in the market, VLC is installed but I never use it.
For the last few months, I wasn't able to shut down my PC, every time I try to do so, the fans start spinning so fast and it hangs, so I just press the shut down button, that problem was only on shutdown, not restart I didn't even bother trying to solve the problem.
Today, while I was working, I noticed the fans doing the same thing that they normally do while shutting down. I ran top noticed 2 vlc instances being run under my username consuming like 122% cpu each, although again I don't use vlc, and I'm not using any program that relies on vlc.
I tried to sudo kill <pid> and sudo killall <pid> and sudo killall vlc but still they weren't killed, that never happened to me before. I killed them from Ubuntu resource monitor, they were killed and the shutdown problem was fixed, and everything went back to normal.
Did that happen to anybody before?
16.04 unity vlc process
asked yesterday
LynobLynob
2,590125192
I'm on ubuntu 16.04 unity latest updates installed, I have one of the best Asus gaming laptops in the market, VLC is installed but I never use it.
For the last few months, I wasn't able to shut down my PC, every time I try to do so, the fans start spinning so fast and it hangs, so I just press the shut down button, that problem was only on shutdown, not restart I didn't even bother trying to solve the problem.
Today, while I was working, I noticed the fans doing the same thing that they normally do while shutting down. I ran top noticed 2 vlc instances being run under my username consuming like 122% cpu each, although again I don't use vlc, and I'm not using any program that relies on vlc.
I tried to sudo kill <pid> and sudo killall <pid> and sudo killall vlc but still they weren't killed, that never happened to me before. I killed them from Ubuntu resource monitor, they were killed and the shutdown problem was fixed, and everything went back to normal.
Did that happen to anybody before?
16.04 unity vlc process
16.04 unity vlc process
asked yesterday
LynobLynob
2,590125192
asked yesterday
LynobLynob
2,590125192
edited yesterday
Lynob
asked yesterday
LynobLynob
2,590125192
asked yesterday
LynobLynob
2,590125192
asked yesterday
LynobLynob
2,590125192
2,590125192
Hi, Lynob, I just updated the script in my answer in a way to be compatible with crontab, that by default works with limited number of environment variables... Now, according to my tests, the script works as it is expected.
– pa4080
yesterday
2
If you're interested in finding out why it's happening, you could runps aux | grep " $(echo -n $(pgrep vlc | xargs ps -o ppid | tail -n +2 | tr -d ' ') | sed 's/ / \| /g') "next time it happens. This would find all running instances of VLC, get the parent PIDs for each of them, and then search for the parent PIDs in the output ofps aux. It might help in tracking down the problem.
– anonymoose
yesterday
3
For the record,sudo kill -9 <pid>would probably have worked where justkilldidn't. The-9means "Kill anything that moves, with extreme prejudice, in the most gruesome way possible". Not much can survive it. Without-9, it's more like "Please die? Please, pretty please with a cherry on top?"
– trysis
yesterday
1
@trysis: Be careful withkill -9, it's dangerous. If for example the application has created a temporary file under/var/lock, it won't be removed. Similarly, buffers won't be flushed, database transactions will not be committed, etc. You could end up with corrupt or missing data if anything was being written anywhere. VLC is probably not doing any of those things, but I would recommend trying to understand the problem before assuming.
– Kevin
yesterday
1
BTW, 99% problems I had with VLC hanging and doing other "strange stuff" were due to it trying to use hardware acceleration for video decoding, or using the "wrong" (whatever that may mean) video backend; I'd try to fiddle with that stuff (disable HW acceleration for codecs, try to change video output backend) and see if anything good comes from it.
– Matteo Italia
yesterday
|
show 4 more comments
Hi, Lynob, I just updated the script in my answer in a way to be compatible with crontab, that by default works with limited number of environment variables... Now, according to my tests, the script works as it is expected.
– pa4080
yesterday
2
If you're interested in finding out why it's happening, you could runps aux | grep " $(echo -n $(pgrep vlc | xargs ps -o ppid | tail -n +2 | tr -d ' ') | sed 's/ / \| /g') "next time it happens. This would find all running instances of VLC, get the parent PIDs for each of them, and then search for the parent PIDs in the output ofps aux. It might help in tracking down the problem.
– anonymoose
yesterday
3
For the record,sudo kill -9 <pid>would probably have worked where justkilldidn't. The-9means "Kill anything that moves, with extreme prejudice, in the most gruesome way possible". Not much can survive it. Without-9, it's more like "Please die? Please, pretty please with a cherry on top?"
– trysis
yesterday
1
@trysis: Be careful withkill -9, it's dangerous. If for example the application has created a temporary file under/var/lock, it won't be removed. Similarly, buffers won't be flushed, database transactions will not be committed, etc. You could end up with corrupt or missing data if anything was being written anywhere. VLC is probably not doing any of those things, but I would recommend trying to understand the problem before assuming.
– Kevin
yesterday
1
BTW, 99% problems I had with VLC hanging and doing other "strange stuff" were due to it trying to use hardware acceleration for video decoding, or using the "wrong" (whatever that may mean) video backend; I'd try to fiddle with that stuff (disable HW acceleration for codecs, try to change video output backend) and see if anything good comes from it.
– Matteo Italia
yesterday
Hi, Lynob, I just updated the script in my answer in a way to be compatible with crontab, that by default works with limited number of environment variables... Now, according to my tests, the script works as it is expected.
– pa4080
yesterday
Hi, Lynob, I just updated the script in my answer in a way to be compatible with crontab, that by default works with limited number of environment variables... Now, according to my tests, the script works as it is expected.
– pa4080
yesterday
2
2
If you're interested in finding out why it's happening, you could run
ps aux | grep " $(echo -n $(pgrep vlc | xargs ps -o ppid | tail -n +2 | tr -d ' ') | sed 's/ / \| /g') " next time it happens. This would find all running instances of VLC, get the parent PIDs for each of them, and then search for the parent PIDs in the output of ps aux. It might help in tracking down the problem.– anonymoose
yesterday
If you're interested in finding out why it's happening, you could run
ps aux | grep " $(echo -n $(pgrep vlc | xargs ps -o ppid | tail -n +2 | tr -d ' ') | sed 's/ / \| /g') " next time it happens. This would find all running instances of VLC, get the parent PIDs for each of them, and then search for the parent PIDs in the output of ps aux. It might help in tracking down the problem.– anonymoose
yesterday
3
3
For the record,
sudo kill -9 <pid> would probably have worked where just kill didn't. The -9 means "Kill anything that moves, with extreme prejudice, in the most gruesome way possible". Not much can survive it. Without -9, it's more like "Please die? Please, pretty please with a cherry on top?"– trysis
yesterday
For the record,
sudo kill -9 <pid> would probably have worked where just kill didn't. The -9 means "Kill anything that moves, with extreme prejudice, in the most gruesome way possible". Not much can survive it. Without -9, it's more like "Please die? Please, pretty please with a cherry on top?"– trysis
yesterday
1
1
@trysis: Be careful with
kill -9, it's dangerous. If for example the application has created a temporary file under /var/lock, it won't be removed. Similarly, buffers won't be flushed, database transactions will not be committed, etc. You could end up with corrupt or missing data if anything was being written anywhere. VLC is probably not doing any of those things, but I would recommend trying to understand the problem before assuming.– Kevin
yesterday
@trysis: Be careful with
kill -9, it's dangerous. If for example the application has created a temporary file under /var/lock, it won't be removed. Similarly, buffers won't be flushed, database transactions will not be committed, etc. You could end up with corrupt or missing data if anything was being written anywhere. VLC is probably not doing any of those things, but I would recommend trying to understand the problem before assuming.– Kevin
yesterday
1
1
BTW, 99% problems I had with VLC hanging and doing other "strange stuff" were due to it trying to use hardware acceleration for video decoding, or using the "wrong" (whatever that may mean) video backend; I'd try to fiddle with that stuff (disable HW acceleration for codecs, try to change video output backend) and see if anything good comes from it.
– Matteo Italia
yesterday
BTW, 99% problems I had with VLC hanging and doing other "strange stuff" were due to it trying to use hardware acceleration for video decoding, or using the "wrong" (whatever that may mean) video backend; I'd try to fiddle with that stuff (disable HW acceleration for codecs, try to change video output backend) and see if anything good comes from it.
– Matteo Italia
yesterday
|
show 4 more comments
1 Answer
1
active
oldest
votes
I'm experiencing similar problem with VLC player. But the difference is I'm using it often. Here is one possible (not fully proofed) workaround for this issue on Ubuntu 16.04 with Unity.
According to this answer we can test whether there is a running application desktop file named vlc or so. If there is no one we can try to kill all VLC's processes. For this purposes create an executable file, named ~/bin/vlc-killer.sh, and add the following lines as its content (here is a reference about the exported envvars):
#!/bin/bash
# Check whether the user is logged-in: if not then exit
if [[ -z "$(pgrep gnome-session -n -U $UID)" ]]; then exit; fi
# Export the current desktop session environment variables
export $(xargs -0 -a "/proc/$(pgrep gnome-session -n -U $UID)/environ")
# Test whether there is any VLC RunningApplicationsDesktopFile
/usr/bin/qdbus org.ayatana.bamf /org/ayatana/bamf/matcher
org.ayatana.bamf.matcher.RunningApplicationsDesktopFiles | grep -q 'vlc'
# If not killall VLC processes
if [[ $? -ne 0 ]]; then /usr/bin/killall vlc; fi
Then open the user's Crontab for edit (crontab -e) and apply the following job (that will execute our script each minute) at the bottom:
* * * * * $HOME/bin/vlc-killer.sh >/dev/null 2>&1
answered yesterday
pa4080pa4080
13.5k52562
1
If I'm right this works only when at least one instance ofvlcwas started via the GUI. If you are used to runvlc movie.mpgsolely from the command line (like I am) this will kill thevlcprocess after a minute. However, nice solution and +1 anyway.
– PerlDuck
yesterday
2
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
1
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107423%2fis-this-behaviour-of-vlc-normal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'm experiencing similar problem with VLC player. But the difference is I'm using it often. Here is one possible (not fully proofed) workaround for this issue on Ubuntu 16.04 with Unity.
According to this answer we can test whether there is a running application desktop file named vlc or so. If there is no one we can try to kill all VLC's processes. For this purposes create an executable file, named ~/bin/vlc-killer.sh, and add the following lines as its content (here is a reference about the exported envvars):
#!/bin/bash
# Check whether the user is logged-in: if not then exit
if [[ -z "$(pgrep gnome-session -n -U $UID)" ]]; then exit; fi
# Export the current desktop session environment variables
export $(xargs -0 -a "/proc/$(pgrep gnome-session -n -U $UID)/environ")
# Test whether there is any VLC RunningApplicationsDesktopFile
/usr/bin/qdbus org.ayatana.bamf /org/ayatana/bamf/matcher
org.ayatana.bamf.matcher.RunningApplicationsDesktopFiles | grep -q 'vlc'
# If not killall VLC processes
if [[ $? -ne 0 ]]; then /usr/bin/killall vlc; fi
Then open the user's Crontab for edit (crontab -e) and apply the following job (that will execute our script each minute) at the bottom:
* * * * * $HOME/bin/vlc-killer.sh >/dev/null 2>&1
answered yesterday
pa4080pa4080
13.5k52562
1
If I'm right this works only when at least one instance ofvlcwas started via the GUI. If you are used to runvlc movie.mpgsolely from the command line (like I am) this will kill thevlcprocess after a minute. However, nice solution and +1 anyway.
– PerlDuck
yesterday
2
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
1
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
add a comment |
I'm experiencing similar problem with VLC player. But the difference is I'm using it often. Here is one possible (not fully proofed) workaround for this issue on Ubuntu 16.04 with Unity.
According to this answer we can test whether there is a running application desktop file named vlc or so. If there is no one we can try to kill all VLC's processes. For this purposes create an executable file, named ~/bin/vlc-killer.sh, and add the following lines as its content (here is a reference about the exported envvars):
#!/bin/bash
# Check whether the user is logged-in: if not then exit
if [[ -z "$(pgrep gnome-session -n -U $UID)" ]]; then exit; fi
# Export the current desktop session environment variables
export $(xargs -0 -a "/proc/$(pgrep gnome-session -n -U $UID)/environ")
# Test whether there is any VLC RunningApplicationsDesktopFile
/usr/bin/qdbus org.ayatana.bamf /org/ayatana/bamf/matcher
org.ayatana.bamf.matcher.RunningApplicationsDesktopFiles | grep -q 'vlc'
# If not killall VLC processes
if [[ $? -ne 0 ]]; then /usr/bin/killall vlc; fi
Then open the user's Crontab for edit (crontab -e) and apply the following job (that will execute our script each minute) at the bottom:
* * * * * $HOME/bin/vlc-killer.sh >/dev/null 2>&1
answered yesterday
pa4080pa4080
13.5k52562
1
If I'm right this works only when at least one instance ofvlcwas started via the GUI. If you are used to runvlc movie.mpgsolely from the command line (like I am) this will kill thevlcprocess after a minute. However, nice solution and +1 anyway.
– PerlDuck
yesterday
2
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
1
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
add a comment |
I'm experiencing similar problem with VLC player. But the difference is I'm using it often. Here is one possible (not fully proofed) workaround for this issue on Ubuntu 16.04 with Unity.
According to this answer we can test whether there is a running application desktop file named vlc or so. If there is no one we can try to kill all VLC's processes. For this purposes create an executable file, named ~/bin/vlc-killer.sh, and add the following lines as its content (here is a reference about the exported envvars):
#!/bin/bash
# Check whether the user is logged-in: if not then exit
if [[ -z "$(pgrep gnome-session -n -U $UID)" ]]; then exit; fi
# Export the current desktop session environment variables
export $(xargs -0 -a "/proc/$(pgrep gnome-session -n -U $UID)/environ")
# Test whether there is any VLC RunningApplicationsDesktopFile
/usr/bin/qdbus org.ayatana.bamf /org/ayatana/bamf/matcher
org.ayatana.bamf.matcher.RunningApplicationsDesktopFiles | grep -q 'vlc'
# If not killall VLC processes
if [[ $? -ne 0 ]]; then /usr/bin/killall vlc; fi
Then open the user's Crontab for edit (crontab -e) and apply the following job (that will execute our script each minute) at the bottom:
* * * * * $HOME/bin/vlc-killer.sh >/dev/null 2>&1
answered yesterday
pa4080pa4080
13.5k52562
I'm experiencing similar problem with VLC player. But the difference is I'm using it often. Here is one possible (not fully proofed) workaround for this issue on Ubuntu 16.04 with Unity.
According to this answer we can test whether there is a running application desktop file named vlc or so. If there is no one we can try to kill all VLC's processes. For this purposes create an executable file, named ~/bin/vlc-killer.sh, and add the following lines as its content (here is a reference about the exported envvars):
#!/bin/bash
# Check whether the user is logged-in: if not then exit
if [[ -z "$(pgrep gnome-session -n -U $UID)" ]]; then exit; fi
# Export the current desktop session environment variables
export $(xargs -0 -a "/proc/$(pgrep gnome-session -n -U $UID)/environ")
# Test whether there is any VLC RunningApplicationsDesktopFile
/usr/bin/qdbus org.ayatana.bamf /org/ayatana/bamf/matcher
org.ayatana.bamf.matcher.RunningApplicationsDesktopFiles | grep -q 'vlc'
# If not killall VLC processes
if [[ $? -ne 0 ]]; then /usr/bin/killall vlc; fi
Then open the user's Crontab for edit (crontab -e) and apply the following job (that will execute our script each minute) at the bottom:
* * * * * $HOME/bin/vlc-killer.sh >/dev/null 2>&1
answered yesterday
pa4080pa4080
13.5k52562
edited yesterday
answered yesterday
pa4080pa4080
13.5k52562
answered yesterday
pa4080pa4080
13.5k52562
answered yesterday
pa4080pa4080
13.5k52562
13.5k52562
1
If I'm right this works only when at least one instance ofvlcwas started via the GUI. If you are used to runvlc movie.mpgsolely from the command line (like I am) this will kill thevlcprocess after a minute. However, nice solution and +1 anyway.
– PerlDuck
yesterday
2
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
1
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
add a comment |
1
If I'm right this works only when at least one instance ofvlcwas started via the GUI. If you are used to runvlc movie.mpgsolely from the command line (like I am) this will kill thevlcprocess after a minute. However, nice solution and +1 anyway.
– PerlDuck
yesterday
2
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
1
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
1
1
If I'm right this works only when at least one instance of
vlc was started via the GUI. If you are used to run vlc movie.mpg solely from the command line (like I am) this will kill the vlc process after a minute. However, nice solution and +1 anyway.– PerlDuck
yesterday
If I'm right this works only when at least one instance of
vlc was started via the GUI. If you are used to run vlc movie.mpg solely from the command line (like I am) this will kill the vlc process after a minute. However, nice solution and +1 anyway.– PerlDuck
yesterday
2
2
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
@PerlDuck, while there is an active VLC "icon" (in Dash launcher) the script works, no matter whether VLC is started by a .desktop file or by CLI.
– pa4080
yesterday
1
1
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
Oh, cool. I wasn't aware of that.
– PerlDuck
yesterday
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107423%2fis-this-behaviour-of-vlc-normal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hi, Lynob, I just updated the script in my answer in a way to be compatible with crontab, that by default works with limited number of environment variables... Now, according to my tests, the script works as it is expected.
– pa4080
yesterday
2
If you're interested in finding out why it's happening, you could run
ps aux | grep " $(echo -n $(pgrep vlc | xargs ps -o ppid | tail -n +2 | tr -d ' ') | sed 's/ / \| /g') "next time it happens. This would find all running instances of VLC, get the parent PIDs for each of them, and then search for the parent PIDs in the output ofps aux. It might help in tracking down the problem.– anonymoose
yesterday
3
For the record,
sudo kill -9 <pid>would probably have worked where justkilldidn't. The-9means "Kill anything that moves, with extreme prejudice, in the most gruesome way possible". Not much can survive it. Without-9, it's more like "Please die? Please, pretty please with a cherry on top?"– trysis
yesterday
1
@trysis: Be careful with
kill -9, it's dangerous. If for example the application has created a temporary file under/var/lock, it won't be removed. Similarly, buffers won't be flushed, database transactions will not be committed, etc. You could end up with corrupt or missing data if anything was being written anywhere. VLC is probably not doing any of those things, but I would recommend trying to understand the problem before assuming.– Kevin
yesterday
1
BTW, 99% problems I had with VLC hanging and doing other "strange stuff" were due to it trying to use hardware acceleration for video decoding, or using the "wrong" (whatever that may mean) video backend; I'd try to fiddle with that stuff (disable HW acceleration for codecs, try to change video output backend) and see if anything good comes from it.
– Matteo Italia
yesterday