crew-stable test failure in ubuntu 12.10

Giorgos Keramidas gkeramidas at gmail.com
Sun Feb 3 14:51:43 CST 2013


On 2013-02-03 14:40, Matt Mackall <mpm at selenic.com> wrote:
>On Sun, 2013-02-03 at 21:22 +0100, Giorgos Keramidas wrote:
>> The biggest consumer of inotify instances seems to be Chrome so far,
>> but this is a very quick and dirty way of crawling /proc:
>> 
>> : 0203 21:19 saturn:/proc$ find . -exec ls -ld {} + 2>/dev/null | fgrep notify | \
>> :   fgrep gkeramidas | sed -e 's@/fd/.*@@' -e 's at .*\./@@' | grep '^[0-9]'  | \
>> :   awk '{print $1}' | fgrep -v /exe | \
>> :   while read pp ; do \
>> :     cat $pp/cmdline | awk '{print $1}' ; \
>> :   done | \
>> :   sort | uniq -c | sort -nr
>> :      72 /opt/google/chrome/chrome
>> :       7 /usr/lib/gnome-settings-daemon/gnome-settings-daemon
>> :       6 kdeinit4:
>> :       5 update-notifier
>> :       4 xfce4-terminal--geometry=100x62
>> :       4 /usr/bin/pulseaudio--start--log-target=syslog
>> :       4 /usr/bin/gnome-screensaver--no-daemon
>> :       3 zeitgeist-datahub
>> :       3 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
>> :       3 /usr/lib/gvfs/gvfsd-trash--spawner:1.7/org/gtk/gvfs/exec_spaw/0
>> :       3 /usr/bin/signon-ui
>> :       2 /bin/dbus-daemon--config-file=/etc/at-spi2/accessibility.conf--nofork--print-address3
>> :       2 //bin/dbus-daemon--fork--print-pid5--print-address7--session
>> : 0203 21:19 saturn:/proc$
>> 
>> I'll dig a bit more, and see if there's anything we can do from our side
>> about it, or if this is not something Mercurial should care about at all.
> 
> Looks like a flagrant Chrome bug to me. I assume you're not running 72
> copies of Chrome or even have 72 tabs open.

Of course not.  I'm looking at a window with 3 tabs right now, so this
is either some form of greedy pre-allocation of inotify instances when
Chrome tries to play 'smart' or a bug.




More information about the Mercurial-devel mailing list