Sending too large messages results in "Disconnected" and exit()
Submitted by Philip Van Hoof
Assigned to D-Bus Maintainers
When you dbus_g_method_send_reply a DBusMessage that is over around 160MB in size.
Because getting the current size of a DBusMessage is either deprecated or not easily possible in the API (without first marshaling, meaning a performance impact just to know the predicted size right in front of sending it - which will do a marshal again), and because there's zero clarity about what the actual maximum message size is (the one in session.conf is apparently not relevant at all), I conclude that this is a bug.
Please either create clarity, make it possible to get the size of your DBusMessage and make it possible to compare that size against a well defined max, or don't exit() my process without any warning whatsoever.