mem used frozen, swapused jumping

[qubodup]

Hi,

With my current setup, often the mem widget displaying mem_now.used value freezes and instead mem_now.swapused flashes during the update step, showing the current mem_now.used value, for some reason in the color (markup) of the mem widget.

Video:
http://youtu.be/YRNpK-6pgJg
Note: the flashing yellow value does change, although it's not identical to htop. In the video it's 1317 at first, changes to values like 1310, 1311 later, while the left constant yellow value stays the same, as it seems, the memused value when awesome starts/rc.lua runs.

Example screens:

rc.lua:
http://codepad.org/qICre4sQ

theme:
http://codepad.org/ysmWeejM

I think it has to do with using the mem widget twice. Perhaps because of non-local variables (entirely guessing) in https://github.com/copycat-killer/lain/blob/master/widgets/mem.lua

Is one supposed not to use a widget twice?

[lcpz]

Is one supposed not to use a widget twice?

For this widget, yes.

This is the same situation as in #61: you're causing a race condition.

Rewrite your widgets like this:

-- memory/swap
memicon = wibox.widget.imagebox(beautiful.widget_mem)
swapicon = wibox.widget.imagebox(beautiful.widget_fs)
swapwidget = wibox.widget.textbox()
memwidget = lain.widgets.mem({
    timeout = 0.5,
    settings = function()
        widget:set_markup(markup("#e0da37", mem_now.used .. "MB "))
        swapwidget:set_markup(markup("#80d9d8", mem_now.swapused .. "MB "))
    end
})

It would be easy to make the widget asynchronous, but I prefer not in order to avoid such bad habits.

[qubodup]

This solves it, thanks!