After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 774988 - Stutter every 10 seconds when fsyncing .goutputstream-XXXXX file
Stutter every 10 seconds when fsyncing .goutputstream-XXXXX file
Status: RESOLVED DUPLICATE of bug 733780
Product: totem
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-11-24 08:36 UTC by unrud
Modified: 2017-06-23 08:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backtrace (423 bytes, text/plain)
2016-11-24 08:37 UTC, unrud 		Details
backtrace (1.17 KB, text/plain)
2016-11-24 08:39 UTC, unrud 		Details

Description unrud 2016-11-24 08:36:00 UTC 
While playing a video Totem writes to the file $HOME/.config/totem/.goutputstream-XXXX every 10 seconds. This apparently happens in the main loop. Unfortunately the file gets also fsynced, which is a slow operation and causes stutter of the video.

On my system the calls to fsync take about 50ms most of the times, but sometimes it's as high as 300ms (which is very noticeable).

I'm using version 3.22.0 on Fedora 25.

A stack backtrace is attached.
Comment 1 unrud 2016-11-24 08:37:35 UTC 
Created attachment 340669 [details]
backtrace
Comment 2 unrud 2016-11-24 08:39:04 UTC 
Created attachment 340670 [details]
backtrace
Comment 3 unrud 2016-11-24 18:27:19 UTC 
The problem is caused by the usage of g_file_replace (https://developer.gnome.org/gio/stable/GFile.html#g-file-replace) in the function totem_pl_parser_save_xspf (https://git.gnome.org/browse/totem-pl-parser/tree/plparse/totem-pl-parser-xspf.c#n103).

The temporary file gets fsynced before it's moved to the target location.
Comment 4 Bastien Nocera 2017-06-23 08:22:07 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 733780 ***