Curious second instance of mplayer
Hello, when I start a movie in mplayer, 2 mplayer processes are started:
Code:
$ pidof mplayer I do have the mplayer cache enabled (2MB). Haven't tried disabling it yet, to see if the second instance of mplayer is still started. Ok, I disabled mplayer cache. Didn't have to restart the movie, and the second mplayer process vanished. Interesting. |
Maybe mplayer uses a thread, after all the PIDs are sequential, so the fist one is the one you started when you invoked the command line and the second one is either a thread or a child process which mplayer chooses to use as part of it's architecture. Makes sense considering what you mention as far as usage statistics. What happens if you exit the program normally? Nothing like that? If you kill the first one, does the second one disappear right away? And if you use "ps -ef | grep mplayer" do you find that the second mplayer PID has the first one as it's parent?
|
Code:
$ ps -ef | grep mplayer Code:
~/src/qt$ pidof mplayer |
My take is that this shouldn't be a gripe to you if you were concerned that it was a problem that is. It seems to be just as I was guessing, the top process forks a child or creates a worker thread. Hey if it didn't do that, then the UI widgets to control things would not work efficiently because it'd be spending too much time playing the media. Or vice-versa, the playing of the media would be interrupted whenever you do small things like adjust the sound or something.
|
Nope, no gripe. It was going to be a question, then decided to look a little deeper into it, and realized this must be normal behavior. Apparently, enabling buffering requires a second instance of mplayer.
You would think buffering ability would be included into a single instance of the program. |
All times are GMT -5. The time now is 01:54 AM. |