and the same, but new_item_separator instead of new_item_normal.
This is the libdbusmenu-glib / libdbusmenu-gtk code, so reassigning accordingly.
There is also going a very intensive D-Bus exchange between the indicator and the owncloud process, it did not look sane to me, so it may be another bug somewhere.
According to massif, the memory allocations come from the following path:
0x1FF8C3AA: new_item_normal (client.c:1095) get_properties_ new_cb (client.c:1578) callback (client.c:698)
0x201A8798: menuitem_
0x201A6C67: get_properties_
0x06CB54E1: g_task_return_now (gtask.c:1121)
[...]
and the same, but new_item_separator instead of new_item_normal.
This is the libdbusmenu-glib / libdbusmenu-gtk code, so reassigning accordingly.
There is also going a very intensive D-Bus exchange between the indicator and the owncloud process, it did not look sane to me, so it may be another bug somewhere.