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 165396 - Nautilus blocks for several seconds on the property page of an avi file
Nautilus blocks for several seconds on the property page of an avi file
Status: RESOLVED DUPLICATE of bug 335533
Product: totem
Classification: Core
Component: GStreamer backend
1.1.x
Other All
: High normal
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2005-01-27 12:16 UTC by Diego González
Modified: 2006-09-10 12:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Diego González 2005-01-27 12:16:34 UTC
i think that the causing is the audio/video propiertes page, shouldn't the
process of extracting the information of a file asynchronous so that nautilus
doesn't block waiting for the information?

also while this is happing no redraw of the windows already opened occours, it
gives the impression to be clunky.
Comment 1 Sebastien Bacher 2005-01-30 16:51:46 UTC
not sure if that's a nautilus or a totem issue (which provides the extension) ...
Comment 2 Christian Neumair 2005-06-03 06:28:55 UTC
Hrm since the whole widget packing and layouting of the property pages is up to
the extension providers, I'm pretty much convinved that this is a totem issue.
Comment 3 Ronald Bultje 2005-06-03 07:40:50 UTC
Oh, this can happen if the movie is missing an index; we rebuild the index then,
which obviously shouldn't be done if we only want metadata...
Comment 4 Tim-Philipp Müller 2006-07-03 16:44:37 UTC
Marking as GStreamer-0.8 issue, since in GStreamer-0.10 the scanning would be done in a separate thread and shouldn't block the UI.

Diego, can you confirm that this is no longer an issue with totem + GStreamer-0.10 backend?
Comment 5 Tim-Philipp Müller 2006-09-10 12:23:38 UTC
Actually, this doesn't seem to be related to the backend after all.

The GStreamer-0.10 backend _could_ do this asynchroneously if it wanted to, but doesn't because blocking is how totem wants it as I understand it. The blocking will happen in totem_properties_view_set_location() and will occur for xine as well (although xine might be smarter about the index rebuilding than GStreamer, but the issue would probably still be there for slow-to-respond sources).

Could be worked around if we move the _play() stuff in totem-properties-view.c into a separate thread I guess.
Comment 6 Bastien Nocera 2006-09-10 12:28:24 UTC
Even better would be out-of-process as in bug #335533
Comment 7 Tim-Philipp Müller 2006-09-10 12:41:23 UTC
> Even better would be out-of-process as in bug #335533

Absolutely, shall we mark this as dup then?
Comment 8 Bastien Nocera 2006-09-10 12:45:55 UTC
(In reply to comment #7)
> > Even better would be out-of-process as in bug #335533
> 
> Absolutely, shall we mark this as dup then?

Go ahead.
Comment 9 Tim-Philipp Müller 2006-09-10 12:56:31 UTC

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