Confirming with latest karmic. This is a regression from jaunty.

I have several Matroska Video (.mkv) containers with x264 video and AC-3
audio, size ca. 1.5 GB, and this happens with all of them.

The bug is only triggered when Nautilus setting for "Preview > Other
Previewable Files > Show thumbnails" is set to something else than
"never". Even if it's set to "Local files only" and "Only for smaller
files than": "5 MB",  I get the bug.

There are different manifestations of this bug.

The most reproducible for me:
1. Open folder with big video file in nautilus
2. Double-click on it, so that totem will start
3. It takes an unusual amount of time until totem starts playing the video
4. Observe e.g. with "top" that nautilus starts using more memory, until all 
RAM is full, after which nautilus will have near 100% CPU as well.

Other way I experience this bug, but not reproducibly. Could depend on the 
exact sequence of starting and closing nautilus and movie players...
Here is how I hit it just before:
1. Open folder with big video file in nautilus
2. Open movie in mplayer from nautllus (right click -> open with)
3. Watch movie
4. Close mplayer, close nautilus folder window
5. Open nautilus, navigate to same folder again
6. Folder opens, but contents do not get displayed; high constant HDD activity, 
full RAM + CPU usage by nautilus, until it hangs.

I hit the same problems as the reporter regarding obtaining a backtrace
with gdb. Could this have something to do with the threads created (see
end of attached gdb log by LoonyPhoenix).

I am marking this as confirmed for now. Could you Pedro or anybody else
provide guidance on how to obtain a correct backtrace here?

** Changed in: nautilus (Ubuntu)
       Status: Incomplete => Confirmed

-- 
nautilus hangs consuming lots of memory and cpu when opening large video files
https://bugs.launchpad.net/bugs/412040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to