[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#626780: icewm: xorg crashes when an application sets a really long title



On 2011-09-25 12:42 +0200, Julien Cristau wrote:

> On Sun, May 15, 2011 at 10:41:46 +0200, arno renevier wrote:
>
>> When a window sets a really long title, icewm (or xorg, I'm not sure) crashes.
>> This can be triggered by a webpage by setting a long <title></title> content
>> (and it will be set as window title by the browser).
>> To reproduce,
>> visit:
>> http://renevier.net/bugs/icewmcrash.html
>> with either midori or iceweasel (it probably crashes with other browsers, but
>> I did not test)
>> The crash happens when switching to another window.
>> I reproduce it reliably on my x86_64 box.
>> 
>> I'll attach a copy of startx stderr 
>> 
> [...]
>> 
>> Backtrace:
>> 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a38b8]
>> 1: /usr/bin/X (0x400000+0x646e9) [0x4646e9]
>> 2: /lib/libpthread.so.0 (0x7f295b4f6000+0xf020) [0x7f295b505020]
>> 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f2958209000+0x217d9) [0x7f295822a7d9]
>> 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f2958209000+0x23332) [0x7f295822c332]
>> 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f2958209000+0x2be17) [0x7f2958234e17]
>> 6: /usr/bin/X (0x400000+0xdd825) [0x4dd825]
>> 7: /usr/bin/X (0x400000+0xd6c83) [0x4d6c83]
>> 8: /usr/bin/X (0x400000+0x31731) [0x431731]
>> 9: /usr/bin/X (0x400000+0x257de) [0x4257de]
>> 10: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f295a22feed]
>> 11: /usr/bin/X (0x400000+0x25389) [0x425389]
>> Segmentation fault at address 0x18
>> 
>> Fatal server error:
>> Caught signal 11 (Segmentation fault). Server aborting
>> 
> If this still happens with an up to date stack, please get a backtrace
> from gdb following http://wiki.debian.org/XStrikeForce/XserverDebugging
> and file a bug upstream according to
> http://intellinuxgraphics.org/how_to_report_bug.html.  Let us know the
> bug number for tracking.

This is likely the same issue as https://bugs.freedesktop.org/36860
which has been fixed in 2.16.

Cheers,
       Sven



Reply to: