#8 xresources not released for xli

v1.0 (example)
closed
None
5
2015-04-17
2010-08-02
No

When viewing images in worker using xli, a resource with Identifier="<unknown>" is created for each instance and not released when closed.
Consequently, X is eventually unable to serve new clients and must be restarted.

When using xli from commandline, resource Identifier=name of image file, and is released when closed.
These effects may be observed using `xrestop`

worker 2.17.8 (and 2.17.3)
xli 1.17.0-r4
xorg-server 1.7.6 (with xorg-x11 7.4-r1)

window manager is xmonad 0.8.1
built using Gentoo portage

Discussion

  • Ralf Hoffmann

    Ralf Hoffmann - 2010-08-03

    Hi,

    I can't reproduce this problem. On my system both the number of resources and the number of total bytes consumed is stable when switching through different images. Does this also happens when using the display_wrapper for showing images with imagemagick?

    Can you give a small example output of xrestop which illustrates the problem?

    Ralf

     
  • Avid Oblique

    Avid Oblique - 2010-08-04

    Additional info that might be relevant:
    I'm using the largely incomplete radeon driver for an Evergreen GPU.
    There's something very wrong with my dbus/hal configuration regarding worker.
    (I only noticed it recently, so I haven't done my homework on it yet)

    `xrestop -b -m 1` abbreviated

    starting worker:
    0 - Worker ( PID: ? ):
    res_base : oxa00000
    res_mask : ox1fffff
    windows : 71
    GCs : 6
    fonts : 2
    pixmaps : 4
    pictures : 0
    glyphsets : 0
    colormaps : 3
    passive grabs : 0
    cursors : 3
    unknowns : 1
    pixmap bytes : 4109040
    other bytes : ~4064
    total bytes : ~4113104
    doesn't vary significantly during operation, and is removed when worker is closed.

    Using displaywrapper with images, or imagemode with either wrapper but no image selected shows no new resources.

    viewing image with xliwrapper:
    6 - <unknown> ( PID: ? ):
    res_base : oxc00000
    res_mask : ox1fffff
    windows : 0
    GCs : 0
    fonts : 0
    pixmaps : 1
    pictures : 0
    glyphsets : 0
    colormaps : 1
    passive grabs : 0
    cursors : 0
    unknowns : 0
    pixmap bytes : 0
    other bytes : ~24
    total bytes : ~24

    view a second image with xliwrapper:
    6 - <unknown> ( PID: ? ): <- new
    res_base : oxe00000
    res_mask : ox1fffff
    windows : 0
    GCs : 0
    fonts : 0
    pixmaps : 1
    pictures : 0
    glyphsets : 0
    colormaps : 1
    passive grabs : 0
    cursors : 0
    unknowns : 0
    pixmap bytes : 0
    other bytes : ~24
    total bytes : ~24
    7 - <unknown> ( PID: ? ): <- previous
    res_base : oxc00000
    res_mask : ox1fffff
    windows : 0
    GCs : 0
    fonts : 0
    pixmaps : 1
    pictures : 0
    glyphsets : 0
    colormaps : 1
    passive grabs : 0
    cursors : 0
    unknowns : 0
    pixmap bytes : 0
    other bytes : ~24
    total bytes : ~24
    these persist after worker is closed.

     
  • Ralf Hoffmann

    Ralf Hoffmann - 2014-01-08
    • status: open --> closed-invalid
    • Group: --> v1.0 (example)
     
  • Ralf Hoffmann

    Ralf Hoffmann - 2015-02-01
    • status: closed-invalid --> open
     
  • Ralf Hoffmann

    Ralf Hoffmann - 2015-02-01

    reopened, I was able to track it down, it's related to xli only, not display from imagemagick

     
  • Ralf Hoffmann

    Ralf Hoffmann - 2015-04-17
    • status: open --> closed
    • assigned_to: Ralf Hoffmann
     
  • Ralf Hoffmann

    Ralf Hoffmann - 2015-04-17

    fixed in Worker 3.6.1

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks