[dmdsoftware]

Tested it a little bit in the meantime and discovered that the problem doesn't only appears after the mentioned time,  rather random. But for sure, it is not from the beginning of the movie. The more the movie proceeds the chances getting higher that it happens.

Code:

01:33:02.159 T:1469051808   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                            - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                           Error Type: <type 'exceptions.TypeError'>
                                           Error Contents: onPlayBackSeek() takes exactly 2 arguments (3 given)
                                           TypeError: onPlayBackSeek() takes exactly 2 arguments (3 given)
                                           -->End of Python script error report<--
01:33:02.928 T:1521009568   ERROR: CCurlFile::FillBuffer - Failed: HTTP returned error 401
01:33:02.947 T:1571341216  NOTICE: CVideoPlayer::OnExit()
01:33:02.947 T:1571341216  NOTICE: VideoPlayer: eof, waiting for queues to empty
01:33:02.947 T:1571341216  NOTICE: Closing stream player 1
01:33:02.958 T:1443885984  NOTICE: thread end: OMXPlayerAudio::OnExit()
01:33:03.039 T:1571341216  NOTICE: Closing stream player 2
01:33:03.039 T:1479066528   ERROR: OMXPlayerVideo: Got MSGQ_IS_ERROR(-1) Aborting
01:33:03.039 T:1479066528  NOTICE: thread end: video_thread
01:33:03.089 T:1571341216  NOTICE: Closing stream player 3
01:33:03.161 T:1469051808  NOTICE: gdrive-testing: PLAYBACK ENDED
01:33:03.303 T:1944997888   ERROR: Control 50 in window 10025 has been asked to focus, but it can't
01:33:03.563 T:1944997888  NOTICE: CVideoPlayer::CloseFile()
01:33:03.564 T:1944997888  NOTICE: VideoPlayer: waiting for threads to exit
01:33:03.564 T:1944997888  NOTICE: VideoPlayer: finished waiting
01:33:03.565 T:1944997888  NOTICE: CVideoPlayer::CloseFile()t
01:33:03.565 T:1944997888  NOTICE: VideoPlayer: waiting for threads to exit
01:33:03.565 T:1944997888  NOTICE: VideoPlayer: finished waiting
01:33:04.913 T:1469051808  NOTICE: gdrive-testing: 1 Updated watch status local tv db id=1398 playcount=1
01:33:04.914 T:1469051808 WARNING: Attempt to use invalid handle 32
01:33:16.012 T:1479066528  NOTICE: gdrive-testing: Seek 0

Almost looks like a KODI bug because I don't call those two methods, and the code is calling the methods with the wrong number of parameters.  But why randomly?  I would need to reproduce it to capture exactly what is going on.

Generally the back and forth won't work well with Google streams once the buffer fills because they don't tend to like to handle seeks well.  The intention of the streamer option is to bypass this.

Yes, the Error Message seems Kodi related, but isn't the reason for the Player to close, because i looked at it and have several of this error messages in the log every time i use the skip function. So the player just exits without any errorlog. Maybe i have to enable debug mode to force some error output in the log file.
Anyway i think this error shouldn't be top priority.
Maybe if you have some free time to spare and watch a movie in the evening, and you want to try to reproduce the error, just try to use the skip function after round about half of the film has past.
I can't even exclude that it is related to the weak hardware of the RPI, because in the first half of every movie, skipping works like expected.
But like i wrote before, it is not that much of a problem.

Do you had any chance to look at the error with the spreadsheet preventing playback ?

Can you remind me on the spreadsheet issue?

I don't think the pause/+playback issue is related to the hardware.  I've had playback issues in even official google drive apps.  Even youtube.  It's fact the connection has closed due to inactivity.  The streamer class I designed to deal with this down the road by keeping the connection open or to intercept the disconnection and resume where left off in a new connection.