GNOME Bugzilla – Bug 626051
multiple disk access when resizing a window
Last modified: 2016-11-19 12:56:23 UTC
Binary package hint: nautilus if i drag and drop a nautilus window that takes the whole screen to resizing it, and then resizing it again to take the whole screen, I've got multiple disk acess that I don't have with other window like firefox or openoffice. I can see this bug with and without the compiz effects. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sun Jun 27 05:00:11 2010 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: nautilus
Created attachment 167134 [details] what i have in /usr/lib/nautilus
Created attachment 167135 [details] My X session errors
Created attachment 167136 [details] My dependencies
Created attachment 167137 [details] Procmaps
Created attachment 167138 [details] Procstatus
Hmm, seems just hovering the toolbar makes a lot of writes as well. When moving the window is probably because it's saving the size and position of the window but it shouldn't do that for browser windows. Cosimo?
(In reply to comment #6) > Hmm, seems just hovering the toolbar makes a lot of writes as well. > > When moving the window is probably because it's saving the size and position of > the window but it shouldn't do that for browser windows. > > Cosimo? We do save the size and position for browser windows too, though we do it on window close. How do you measure writes and disk access? Would be nice to have a stacktrace of what happens when you move the window or hover the toolbar.
I did a strace on nautilus. How can I make gdb stop on disk write?
Seems the movement on the toolbar was writev and caused by some tooltip function i gtk so skip that one.
Is this still an issue?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!