Problem with playing videos in ALL capable apps

REPRODUCIBILITY (% or how often): Everytime the apps are in use
BUILD ID = OS VERSION (Settings > About product): 4.2.0.21 (Verla)
HARDWARE (XA2, X10, X10 II, …): Xperia XA2 Ultra
UI LANGUAGE: English, German
REGRESSION: (compared to previous public release: Yes, No, ?): YES: Problem since SFOS 4, in SFOS 3 it was never a problem

DESCRIPTION:

Everytime I use an app which can display/play videos (either self-made by camera or downloaded) the apps are crashing at some point during playback. This can happen at any point during the usage:
Either it can be the first video that gets played or some videos afterwards or in seldom cases more than a half an hour later with constant usage of the app.
Affected apps are ALL video play capable apps:
e.g. LLs vPlayer, Sailimgur, picoplayer, Gallery, Gagbook, all available “Filemanagers”, etc.

Some apps that are made for playing Youtube videos only play sound , video not at all any more (may be related)

PRECONDITIONS:

I guess that I have a misconfiguration or broken installation but I can’t find the culprit, since no one else is reporting a similar problem I don’t expect it to be a SFOS bug maybe something went wrong while upgrading from SFOS 3 to SFOS 4?

STEPS TO REPRODUCE:

  1. open app(s)
  2. choose video
  3. repeat playing videos until apps hangs or crashes (usually 3-4 videos)

EXPECTED RESULT:

app(s) play videos without problem, until app get closed by user

ACTUAL RESULT:

app(s) keep crashing sometimes so much that a zombie process is left and the app has to be closed by taskmanager (e.g. Lighthouse)

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

6 Likes

Am I really the only one here with this problem?
Does anyone have some basic advices what to check?
Maybe reinstalling codecs or something similar?

Well you are not the onlyone, I have exact same problem with XA2. Not only video apps crash but also for example ImgOrganizer. I have reinstalled apps over and over again but I think too that something changed/went wrong with update to SF4…

Not sure, if related, but I’m having some issues myself with video playback in the latest versions:

  • Overlay missing in Gallery (making it impossible to skip through the video)
  • jolla-gallery not closing properly after playback and won’t open when trying to play another video

I reached out to the jolla support and they filed internal bug reports, but haven’t heard any more until now. I was wondering, if maybe my gallery config got corrupted causing the issue and if there is a way to reset it, but got no reply on that.

Could be that our issues are related, could be that they are not.

reinstalling apps also didn’t help me at all… It’s either a misconfiguration with the installed codecs. In the past I had problems with Openrepos ugly codecs but they are outdated since SF2.x
So I only use what comes with the installation.
But the fact that restarting the app(s) can make the same video play immediately without any problem or can crash 10x in a row with forced restarts every time makes it so random, unpredictable but an indicator for a bug in my opinion.

I am the maintainer of the GagBook app and I am trying to debug such issues since a long time now. There are some app related bugs that cause some app crashes, but in my opinion the main issues are caused by the underlying libraries provided by SFOS.

I was able to log the following a few SFOS releases ago (on 12th June 2021):

GStreamer-CRITICAL **: 13:24:58.970: gst_query_set_nth_allocation_pool: assertion 'index < array->len' failed

GLib-GObject-WARNING **: 13:24:58:995: invalid cast from 'GstVideoBufferPool' to GstDroidBufferPool'

Hi Alex,
great that you are still active with the app. Can I support you? I constantly use the app and could probably provide you with tons of logs…if that’s helpful. But I really think the problem is on OS level, also the gallery app shows the same problems, even with self made videos.

Updated to 4.4 and still keeps crashing.

4.5 and the issue still remains

1 Like

Don’t you consider a simple reflash?

Not only remains, but also no information on how to debug this behaviour. Even happens on gallery app with videos I took with the xperia 10 ii.

I know this is just stock advice, I’m just curious, have any of you (other than the dev) collected logs for us to see?

In a terminal

  • devel-su
  • start gallery or like
  • journalctl -k -f | grep Fatal

The allocation error noted by @Alex looks deadly but it would be nice to see if it’s consistently that.

2 Likes

I guess not, cause videos are pretty much broken right now, i mean, videos on fb for example lags like crazy, microtube lags like crazy, i have some videos on the phone that are probably 2k and they lag, so i guess it’s the same for most people since the 4.5 update, at least i didn’t have this problem on 4.4

Therefore I thought about a reflash with 4.4.0.72, but unfortunately forgot to write explicitly.

hey @poetaster,

I installed and run 9gag app, it has a lot of videos, and i did the journalctl -k -f | grep Fatal . It took a while but finally it stuck-frozed and after a while the "Wait - Exit"popup appeared on the top of the screen. Nothing appeared on grep. The only log I got without grep was:

[root@Xperia10II-SailfishX defaultuser]# journalctl -k -f 
-- Logs begin at Wed 2023-06-28 14:04:09 EEST. --
Jun 28 14:59:21 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 14:59:23 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 14:59:34 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 14:59:35 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 14:59:36 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 14:59:36 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 14:59:36 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 14:59:45 Xperia10II-SailfishX kernel: BUG: Bad rss-counter state mm:ffffffc0a905db00 idx:4 val:487609
Jun 28 14:59:45 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 14:59:45 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 15:00:04 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107

Since you mention Alex, check his 2 years old comment here: GagBook | OpenRepos.net — Community Repository System

Is there any way to get logs from gstreamer or whatever video player/ system sailfishOS uses ?

You can just do a generic journalctl > log.txt to catch everything and grep through it looking for. Sometimes if I know I can trigger an error I use -r which shows newest entries first. Then I can quickly hit CTRL-C if something shows up since you see it a bit longer. One can also use specifiers to limit to systemd units (-u) or SYSLOG_IDENTIFIERS (-t). and of course, use -g to sepecify a grep pattern (perl style).

EDIT: -g is not supported on device.

If desperate strace :slight_smile: I have to admit I’m not the best at this …

It looks like he’s creating exra logs. But for the sake of simplicity, if the bug is also showing up for the Jolla Gallery, it makes sense to focus on that since it will be familiar to @mal & co. @mal, you any advice for capturing logs for debugging this?

1 Like

I should have linked this:

There you can find a script that produces generic logs. That would probably be the most useful way to proceed.

1 Like

From terminal I did:

journalctl -f

I did run Gallery app and used it for 2 - 3 mins, the logs few seconds before and after the freeze/ crash:

:26095 total_time:2924049 (cc_soc:2724->3456)
Jun 28 16:06:37 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:06:40 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-qt5[5534]: warning: terminating: booster:5976 invoker:7010 socket:20
Jun 28 16:06:40 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-qt5[5534]: warning: Daemon: sending exit(1) to invoker(7010)
Jun 28 16:06:40 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-qt5[5534]: warning: sending SIGTERM to booster (pid=5976)
Jun 28 16:06:40 Xperia10II-SailfishX booster-qt5[5534]: *** signal=17 pid=5534
Jun 28 16:06:40 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 16:06:41 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 16:06:47 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:06:48 Xperia10II-SailfishX kernel: pmi632_charger: somc_aicl_irq_handler: IRQ: aicl-done
Jun 28 16:06:48 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL][LERANING] charge_status:1 msoc:36 bsoc_cp:3531 batt_soc_cp_drop:0 cc_soc_drop:0 hold_time:39141 total_time:2937095 (cc_soc:2724->3456)
Jun 28 16:06:57 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:07:01 Xperia10II-SailfishX kernel: pmi632_charger: somc_aicl_irq_handler: IRQ: aicl-done
Jun 28 16:07:01 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL][LERANING] charge_status:1 msoc:36 bsoc_cp:3531 batt_soc_cp_drop:0 cc_soc_drop:0 hold_time:52170 total_time:2950124 (cc_soc:2724->3456)
Jun 28 16:07:02 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 16:07:03 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 16:07:08 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:07:11 Xperia10II-SailfishX lipstick[5741]: [D] onTriggered:102 - Application "Gallery" with PID 29143 is not responding
Jun 28 16:07:11 Xperia10II-SailfishX lipstick[5741]: [D] onClicked:89 - User terminated the unresponsive application "Gallery" with PID 29143
Jun 28 16:07:12 Xperia10II-SailfishX lipstick[5741]: [D] onClicked:89 - User terminated the unresponsive application "Gallery" with PID 29143
Jun 28 16:07:12 Xperia10II-SailfishX kernel: BUG: Bad rss-counter state mm:ffffffc0a8ddb480 idx:4 val:117958
Jun 28 16:07:12 Xperia10II-SailfishX booster-generic[5542]: *** signal=17 pid=5542
Jun 28 16:07:12 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-generic[5542]: warning: Boosted process (pid=26508) exit(255)
Jun 28 16:07:12 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-generic[5542]: warning: Daemon: sending exit(255) to invoker(29102)
Jun 28 16:07:12 Xperia10II-SailfishX invoker[29102]: warning: application (pid=-1) exit(255) signal(0)
Jun 28 16:07:12 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 16:07:14 Xperia10II-SailfishX kernel: pmi632_charger: somc_aicl_irq_handler: IRQ: aicl-done
Jun 28 16:07:14 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL][LERANING] charge_status:1 msoc:36 bsoc_cp:3547 batt_soc_cp_drop:-16 cc_soc_drop:-13 hold_time:65222 total_time:2963176 (cc_soc:2724->3469)
Jun 28 16:07:14 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL]max bsoc/ccsoc updated. bsoc_cp:3547 ccsoc:3469
^C
[root@Xperia10II-SailfishX defaultuser]#

I played several videos and swap from right to left, I played one video and when I pressed the play button in the ecenter of the screen to rewatch it I got black screen and “Wait - Exit” popup on the top. At “Jun 28 16:07:03” I preessed the play button.

At your disposal for further tries / experiments / investigation!

Also I run collect-logs.sh it created a .tar with 20 .txt files, which one do you believe it could help?

I wonder what’s wrong on the i2c bus? But that’s not relevant (maybe a battery thing?)

All of them :slight_smile: But that’s a general overview of al things. It does contain a journal.txt file which is probably not going to look any different than what you’re getting :slight_smile:

I’m just testing with this combination:

[root@Phone22 defaultuser]# journalctl --no-pager -f _PID=4404
-- Logs begin at Wed 2023-06-28 15:20:52 CEST. --

Jun 28 15:22:32 Phone22 jolla-gallery[4404]: [W] unknown:1154 - file:///usr/lib64/qt5/qml/Sailfish/Silica/PageStack.qml:1154:13: QML Binding: Binding loop detected for property "value"

So, using follow and specifying the _PID (which I grabbed from an initial run of just journalctl) I get updates ONLY for the app as errors related to it pop up.