Comment 17 for bug 347444

Just something I noticed trying to find the cause of the issue: some applications appear to send the icon of the notification in binary form to the dbus channel, for example emesene. The array containing the icon-data can often contain about 10'000 entries, it could be that applications listening to the dbus-channel hang because they take a while to interpret all the data or deadlock in some way?
I cannot reproduce the issue manually sending notifications through notify-send, but on the other hand in this way the icon data does not appear to get sent via dbus. Attached is an example from dbus-monitor, which shows all messages sent on dbus by a simple <user sent a message> notification from emesene.