Thumbnail settings don't work as expected

Bug #40874 reported by Rounan
22
Affects Status Importance Assigned to Milestone
Nautilus
Won't Fix
Low
nautilus (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Hi,

I'm running AMD64 Dapper, up to date.

When I'm downloading a longer video using bittorrent (bittornado client), gnome-video-thumbnailer tries, again and again, to preview the file. This results in my HDD being hit hard, and wild swings in my memory usage every 10 seconds as the process runs and re-runs. When I kill the process, all is well.

I have the preview preferences in nautilus set so it should only be previewing local files under 5MB in size. The intention is to show me previews of my photos, but not waste resources previewing gigabytes of video. Especially not trying to preview the same incomplete file 10 times a minute.

Is there a way to set the preferences so that it will work that way? If so, we need to make the preferences more clear. This behaviour is not as advertised.

Revision history for this message
Rounan (nrcavan) wrote : Ram usage due to thumbnailing

gnome-video-thumbnailer is the culprit.
hda is also being hit to the tune of ~20MB/second.

Revision history for this message
sam tygier (samtygier) wrote :

confirmed in dapper.
there are some mp4 torrents to test with at http://media.ccc.de/filez/congress/2005/lectures/video/mp4/torrents/

Changed in nautilus:
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. That's known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=324656

The preference doesn't apply to video because it doesn't require to download the video to snapshot a frame

If you want to stop using the feature for a mimetype you can use gconf-editor and modify the "/desktop/gnome/thumbnailers/<mimetype>/enable" gconf key

Changed in nautilus:
assignee: nobody → desktop-bugs
Revision history for this message
sam tygier (samtygier) wrote :

i think the problem here is more to do with the thumbnail being remade every few seconds during a download. this results in almost constant processor usage during a download.

Revision history for this message
Sebastien Bacher (seb128) wrote :

You can read bug #1573 which has been fixed on the topic. Is your download slow? Nautilus only start the mechanism after 5 seconds without any change so a slow download hanging could cause that sort of behaviour ...

Revision history for this message
Sebastien Bacher (seb128) wrote :

the number was from bugzilla.ubuntu.com, that's bug #8329 on launchpad now

Revision history for this message
sam tygier (samtygier) wrote :

could that time be set to 10 seconds? that might help a bit.

or could nautilus take into account how recently the thumbnail was updated? for example if we have recieved more than 2 notifications on the last minute then set the timeout to 30 seconds

Revision history for this message
Sebastien Bacher (seb128) wrote :

it could probably be smarter. 10 seconds would give the impression it doesn't work on "normal" situation (like a copy of an image that takes 1 second). Is your issue due to the fact than the download has no activity for 5 seconds or not?

Revision history for this message
sam tygier (samtygier) wrote :

i was downloading with gnome bittorrent client. its quite possible that there where lots of 5 second gaps with no new packets arriving. or is it possible that the gnome bt client caches the data, rather than streaming straight to disk?

Revision history for this message
Sebastien Bacher (seb128) wrote :

maybe, I've not worked on bittorent nor looked at that code

Revision history for this message
Mike Fedyk (mfedyk) wrote :

From duplicate bug 150817:

Proposed solution: If a file has been modified previously in the last N seconds and has been modified again, do not attempt to thumbnail the file.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that's what the code is already supposed to do

"2005-05-08 Martin Wehner <email address hidden>

 * libnautilus-private/nautilus-thumbnails.c:
 (thumbnail_thread_start):
 Don't try to thumbnail files which have been modified in the
 last few seconds to avoid constantly re-thumbnailing them.
 Current cool-off period is three seconds. Fixes bug #107418."

Changed in nautilus:
status: Confirmed → Triaged
Changed in nautilus:
status: Confirmed → Won't Fix
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream closed the bug with this comment

"In general its a bad idea to limit thumbnailing based on file size for most
non-image formats, because the size of the file does not generally indicate how
much you have to read or how much work you have to do to thumbnail it. So, a
500 megabyte pdf with 500 pages is likely as fast to thumbnail as a 1 megabyte
file with one page.

Therefore we do not artificially limit out-of-process thumbnailers. If a
particular thumbnailer requires it it can enforce the limits itself."

Doing the same on the distribution task there

Changed in nautilus:
status: Triaged → Invalid
Revision history for this message
Ryan Fugger (rfugger) wrote :

Still getting this bug in intrepid. The cooling-off period of 3 seconds is not enough to avoid constant 100% cpu usage while downloading torrents with multiple videos and viewing them in a nautilus window.

This has nothing to do with file size, and everything to do with it being silly for the system to be bogged down continually be thumbnailing incomplete and constantly-changing video files. Surely there must be a way to avoid this, while still achieving expected behaviour when simply writing a file once. Bug #8329 mentions only thumbnailing once the file is closed, rather than on every change...?

Changed in nautilus:
status: Invalid → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen closed bugs if you have a similar issue in a new version but open a new bug

Changed in nautilus (Ubuntu):
status: New → Invalid
Changed in nautilus:
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.