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

Bug#709767: xprop: Out of memory for _NET_WM_ICON



Control: reassign -1 mlterm

On Sat, May 25, 2013 at 11:44:49 +0200, Jan Braun wrote:

> Package: x11-utils
> Version: 7.7~1
> Severity: normal
> 
> | $ xprop -id $WINDOWID
> | XdndAware(ATOM) = BITMAP
> | WM_STATE(WM_STATE):
> |                 window state: Normal
> |                 icon window: 0x0
> | _NET_WM_ICON(CARDINAL) = xprop: error: Out of memory!
> | $
> 
> This is in mlterm, which sets $WINDOWID to its window id, so the
> _NET_WM_ICON should be mlterm's icon. Maybe mlterm is doing something
> wrong, but at least openbox shows an icon, so I'm blaming xprop for now.
> 
> stracing shows
> 
> | mmap(NULL, 18446744072239476736, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
> | mmap(NULL, 18446744072239607808, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
> 
> which looks like an integer underflow/conversion error to me. (Full
> strace is attached.)
> 
> I found
> http://lists.freedesktop.org/archives/xdg/2009-January/010165.html
> which talks about _NET_WM_ICON and 32/64 bit confusion and hence may be
> relevant.
> 
Looks like an mlterm bug to me.  It seems to use an array of 32bit
values instead of longs in its XChangeProperty(_NET_WM_ICON) call.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


Reply to: