Bug#249489: nautilus crashes reading some directories

[Max Vozeler]

Hi,

On Sun, Jun 06, 2004 at 08:20:32AM +0200, Ruben Porras wrote:
> El s=E1b, 05-06-2004 a las 22:21, Sebastien Bacher escribi=F3:
> > Could you test if the problem is still here with nautilus 2.6.2 ?
>=20
> Yes, it's still here.

It's still there in 2.6.3-3 too, we hit this bug this afternoon on
my dad's laptop. I can confirm your other findings too: The affected
folder ~/Bild contained a directory "H=FCtte" with non-ASCII characters i=
n
the name. Renaming this folder to any other name even containing the
same non-ASCII characters (eg. "H=FCtte1") made the problem go away.

The locale is set to de_DE.UTF-8.

Also creating new folder with umlauts in the name using nautilus works
without problem, but renaming "H=FCtte1" back to the original name makes
the current window freeze immediately. Creating a new folder with name
of the original folder ("H=FCtte") also works without problem.

Here is part of an strace after the window has frozen.

Process 3778 attached - interrupt to quit
read(3, "\26\0\1\23\245\2\0\1\245\2\0\1\0\0\0\0\0\0\0\0\306\1\244"..., 32=
) =3D 32
read(3, "\f\332\1\23\246\2\0\1\0\0\226\0\306\1\5\0\0\0\235\10\240"..., 32=
) =3D 32
read(3, "\26\0\5\23\246\2\0\1\246\2\0\1\0\0\0\0\0\0\0\0\306\1\244"..., 32=
) =3D 32
read(3, "\f\332\5\23\246\2\0\1\0\0\233\0\306\1\t\0\0\0\235\10\240"..., 32=
) =3D 32
read(3, "\26\0\10\23\245\2\0\1\245\2\0\1\0\0\0\0\0\0\0\0\324\1\244"..., 3=
2) =3D 32
read(3, "\26\0\v\23\246\2\0\1\246\2\0\1\0\0\0\0\0\0\0\0\324\1\244"..., 32=
) =3D 32
read(3, "\f\253\v\23\246\2\0\1\306\1\0\0\16\0\244\0\0\0\235\10\340"..., 3=
2) =3D 32
read(3, "\26\0\r\23\246\2\0\1\246\2\0\1\0\0\0\0\0\0\0\0\325\1\244"..., 32=
) =3D 32

... so it goes until its killed for OOM.

# lsof -p `pidof nautilus`
..
nautilus 5402 karsten    3u  unix 0xc400f940           23461 socket

  nautilus/unstable uptodate 2.6.3-3
  nautilus-data/unstable uptodate 2.6.3-3
  libnautilus2-2/unstable uptodate 2.6.3-3

That's all the notes I had taken. I can do other tests or give more
information later today if you want.

Cheers,
Max

Btw, I just found this upstream bug that looks very similar
  http://bugs.gnome.org/show_bug.cgi?id=3D144485

--=20
308E81E7B97963BCA0E6ED889D5BD511B7CDA2DC