When I have a huge list of media, and it's set to play the next file, when there is a warning from mplayer and "notify mplayer/mpv crashes" is on in advanced preferences, the UI will become unresponsive. Then you have to "force quit" smplayer, even though you can see it's playing the movie that mplayer complained about. Smplayer has already tried to switch to the next media file, but instead it's stuck playing the one it complained about. I looked in the log and it just says something about a video filter not existing, which isn't a fatal error in mplayer. With "notify mplayer/mpv crashes on" the smplayer goes black just double-clicking on the movie to change it from fullscreen and back again. Then you have to click stop then play again to restore the image. But only on certain video files, not all of them.
Could you send the smplayer log (menu View) after this error happens?
here's the log. I know the specific file that generates this error, and if it doesn't crash right away, double clicking on the movie to make it windowed instead of fullscreen crashes it right away.
I can't see any error in the log.
Anyway if you're using the option to add black borders in fullscreen (preferences -> general -> video), try disabling it.
black borders for fullscreen and subtitles is off, so is software equalizer. all other options are on.
Still doesn't work?
the thing is, it works great as long as "notify mplayer/mpv crashes" is turned off. When it's turned on, that non-error error message in the log will crash the interface of smplayer. Then you have to "force quit" the program. With the crash reporting turned on, even if you get the movie to play, then adjust the volume, it pops up that crash message and freezes the UI.
For several years I have had to deal with an unreponsive SMPlayer that must be manually killed! Now I found this bug report almost by accident. Since this option is checked by default (at least for me), so the problem may be seen by many users, why not fix it, or at least let the users know how to work around the bug? This is by far the most user-unfriendly aspect of SMPlayer, and it is such a relief to find this workaround. Even if it is a workaround that does not always work.
I would raise the priority of this bug by quite a bit. Get it fixed already!! You don't have to act like Microsoft or Google and ignore bugs.
Last edit: David Spector 2018-04-04
I'm afraid I can't reproduce this problem in my computer. If someone tells me, step by step, how to reproduce the problem I'd try to fix it.
If you can't reproduce the problem, yet it always happens on my computer, I would say that SMPlayer is sensitive to something in the environment that it should not be. Give me an instrumented version of SMPlayer that produces a script of its input and actions and I'll be happy to run it and send you the resulting file. It should pinpoint the problem, assuming the programmer took the time to put such instrumentation into the program.
If there is no instrumentation, someone is going to have to run SMPlayer under a debugger, and find out where the problem occurs the old-fashioned way.
I will get a copy of a video that makes smplayer crash. I have to go to my friends house, I know he has several that do it. I am a debugging champion, and this bug won't hide for much longer!
wow the bug is alot more difficult to trigger than I thought. I originally thought some packed B Frames would cause the error message to come up, but that doesn't work. I am tentatively saying the b frames in avi combined with thousands of entries in the playlist triggers it. We'll see....
The bug happens for me 100% of the time when the checkbox is checked.
Also, I got this error when I clicked on the ticket link: "503 No
Backend Servers Available
No backend servers were available to answer your request. Please notify
the site admins."
David Spector
On 4/10/2018 2:45 PM, Mat L wrote:
Related
Bugs: #854
Do you have an additional log you can post when the crash happens? Or any other details.
Details: SMPlayer continues running if it was running, or stopped if it
was stopped, but the keyboard and mouse are ignored. The only way to
close SMPlayer is to kill the process.
If SMPlayer creates a log, it doesn't advertise the fact.
Every computer I've ever had has brought out bugs in products, because
as a developer I run several systems-level programs, including a
keyboard macro program that injects itself into all interactive
processes. Unfortunately, most programs aren't instrumented to leave a
log or trace showing what was actually happening when a problem occurred.
On 4/10/2018 6:38 PM, Mat L wrote:
Related
Bugs: #854
There's an option in preferences -> advanced -> Logs to save the log to a file.
If the log is not saved it might be because the crash happened before smplayer could save it.
I got the video file that makes my friends smplayer crash, but it won't make it crash on my machine. We're using the same linux and everything. Next, I will try the video just by itself on my friends computer, and finally the video in a very huge list. Probably going to take a bit to nail down the exact cause of the glitch.
Thank you Mat L for the info about how to save a log. I see that I already
had this option checked. I have no idea where the log was written, since
I don't have a full pathname specified in any of the fields.
Anyway, here's what I did this time:
that I have not had a problem with failure in keyboard and
mouse responsiveness since I have used SMPlayer. I am puzzled.
Windows 8.1, SMPlayer 17.9.0 (32-bit)
The log is saved in the smplayer configuration folder. There's an option in the Help menu to open that folder.
Ricardo Villalba, I opened the Configuration file and see no file with LOG in its name. Too bad there is no advanced help subitem in the Help menu item. I don't know where the explanation of the logging system is hiding and I don't have the time to search for it.
The name should be smplayer_log,txt. Be sure the option "Save SMPlayer log to a file" is enabled.
well, to tell you the truth, I think the UI freezing has stopped. Perhaps it was related to the gnome version. But! not all is well, because instead the smplayer screen goes black and the audio plays, but the video doesn't. On my computer, it displays the video, using the exact same playback method. So, I tried playing it with just mplayer and it worked properly. Summary: mongol plays back perfectly on my computer, but on my friends computer smplayer shows a black screen. If I use mplayer on either machine, it works properly.
Try changing the video output in preferences -> general -> video.
yes, it's true. By setting the render to gl(fast) on his machine it eliminated the black screen, so I suppose the ui bug went away with the old version of gnome and the black screen is fixed by changing the render. nuts!
last night I went to his place and he complained something new had started. The rendering of most movies would start out normal then slow down until the movie seemed paused on a single scene. Once he hit rewind to the beginning it started out and stayed normal. So after some quick testing with the options, changing the render back to "Default" made it work properly again, and putting it on gl(fast) made it fail to render. On my machine here, changing the render to gl or default seems to have no effect on playback. Hopefully this information will be handy.