When attempting to open a wildcarded file on the command line using gvim, the program causes X to rapidly consume all available system memory and processing time until killed. I've encountered the problem a number of times, however I've found it difficult to do useful testing during the system failure because of the extremely slow system response time: On one occasion I managed to halt the destructive behavior by killing gvim and various other desktop applications; I suspect that the prolonged instability after killing gvim was due to the system attempting to free the swap space on the hard drive, rather than a continued system conflict. Two other occurrences of this problem resulted in hard reboots of the system. app-editors/gvim-7.0_alpha20050721 -acl (-aqua) +bash-completion -cscope -debug -gnome -gpm +gtk +gtk2 -motif -mzscheme -netbeans -nextaw -nls +perl -python -qt -ruby (-selinux) -tcltk -termcap-compat x11-base/xorg-x11-6.8.2-r2 -3dfx -3dnow +bitmap-fonts -cjk -debug -dlloader -dmx -doc +font-server -insecure-drivers -ipv6 -minimal +mmx -nls -nocxx +opengl -pam -sdk +sse -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r0, 2.6.11.10 i686) ================================================================= System uname: 2.6.11.10 i686 Intel(R) Pentium(R) 4 CPU 2.66GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=pentium4 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks noinfo notitles sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 arts crypt gif jpeg kdeenablefinal mmx mmx2 nptl nptlonly opengl pcre perl png readline sse sse2 ssl tiff unicode xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Anthony: We need more information and gdb backtraces if possible. What does 'open a wildcarded file' mean?
I was referring to the list of files you'd expect to be generated by Bash upon entering a wildcard as part of a file name: src/Version*.cs In addition to the above, I also attempted to open a nonexistent file using gvim and encountered the same erroneous behavior. On that occasion, I had attempted to open "src/VersionString." As for the backtraces, I'll see if I can capture any of them before the system crashes, but I can't make any guarantees. I tried to capture a backtrace just now and accomplished nothing other than necessitating a reboot. I'll post the test results in subsequent comments since I'm likely to lose my existing remarks.
not sure why you CC'd vim@ when that's who it's assigned to...
Sorry, it wasn't intentional; Firefox's SessionSaver extension is still buggy.
I can't reproduce this one, so I think I'll need a backtrace. Try using X11 forwarding if getting one locally doesn't work.
Please retry with 20050809. If it's still a problem, please reopen with a backtrace.
This problem has been fixed in the newer version, thanks.
