Kodi Community Forum - Files opened dozens of times

Hello guys,

I am using Kodi 17.6 on a FireTV Stick Gen.2 with the Emby for Kodi PlugIn and I am having a issue that randomly cause my Emby Server to crash. The problem is that when I fast forward or skip ahead during streaming Kodi opens the file a dozens of times. Here an output of lost /mountpoint:

Quote:mono-sgen 11004 emby   56r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   62r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   64r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   66r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   68r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   70r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   72r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   74r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   76r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   78r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   80r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   82r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   84r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   86r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv
mono-sgen 11004 emby   88r   REG   0,43 4396941271 8205405326195636191 /mountpoint/testfile.mkv

When I got this output there was only one client streaming one file. It only happens when using Kodi + PlugIn, the official Emby Apps do not cause this issue.
According to the Emby for Kodi developer this is a issue with Kodi and not Emby for Kodi (topic over at Emby Forum: https://emby.media/community/index.php?/...ack-issue/). Is there a way to avoid this problem yet (e.g. using an Alpha/Beta of Leia)?

I am also using a advancedsettings.xml to increase the default Kodi buffer:

Quote:-<advancedsettings>
-<cache>
<buffermode>1</buffermode>
<memorysize>139460608</memorysize>
<readfactor>20</readfactor>
</cache>
</advancedsettings>

Any hint is appreciated, thanks! :-)

To receive meaningful assistance you will need to provide a full debug log.

The instructions are here... debug log (wiki)

If you are using the Basic Method, then ensure the following is applied...
1.Enable debugging in Settings>System Settings>Logging,
2.Restart Kodi
3.Replicate the problem.

If you are using the Advanced Method ensure you have correctly created and applied the advancedsettings.xml file.

In both instances, you should see the word DEBUG throughout the log.

Note: Full logs only. No partial or redacted logs
Do NOT post your logs directly into the forum. Always use a paste site like pastebin.com. Post the link to your pasted log in the forum

Took me more time than I thought.

Here you go -> https://paste.ubuntu.com/p/cx4PQhnz4y/

What I did: I opened the file on Emby and then skip ahead a couple of times and every time I did that a new file was opened at the end the file was opened 10 times. Here the output of lsof /mountpoint: https://paste.ubuntu.com/p/h86PTNYK8c/

I found a lot of this in the log: https://paste.ubuntu.com/p/pJDzg66mHC/
Is this anything to worry about?

If you need anything else, just let me know.

(2018-05-05, 16:46)neik Wrote: [ -> ]Is this anything to worry about?

In a way yes. I'm really interested: which part of the big fat red text above the "Post Reply" is unclear to you? Smile

You did post the URL for the pasted log, and somehow you also plaster a big blob of uncrunchable text onto the forum as well.
We're trying to keep such garbage away from the forum server for a reason, you know.

Also, debug logging needs to be enabled from the start, not somewhere half along the way. So if you do want to debug, enable it, and restart Kodi for a fresh log file.

Judging from the kodi.log itself, it seems more an Ember problem than a Kodi matter to me.
Perhaps others can take a peek at it.

(2018-05-05, 20:51)Klojum Wrote: [ -> ]Also, debug logging needs to be enabled from the start, not somewhere half along the way. So if you do want to debug, enable it, and restart Kodi for a fresh log file.

Judging from the kodi.log itself, it seems more an Ember problem than a Kodi matter to me.
Perhaps others can take a peek at it.

I was pretty sure to have debug activated but apparently something went wrong, sorry for that and the text in the post above (it's edited now).

I will have a look at it again and try to create a proper debug log. Thanks so far!

€dit: Just had a look at the log and saw that on line 25 there is already a debug entry. Are you sure debug is not activated?

That's a different kind of debug entry... Sorry. Wink

In the Kodi.log:

Line 60: 11:38:36.486 T:18446744072490812648 NOTICE: Disabled debug logging due to GUI setting. Level 0.

Line 339: 11:41:31.432 T:18446744072490812648 NOTICE: Enabled debug logging due to GUI setting. Level 2.

It's only 3 seconds, but still, gotta be precise Smile