It is possible for the log attributes when serialized using the custom serialize(), toBSON(), etc. members to trigger a BSONObjectTooLarge exception. Ideally the log line truncation performed by the logging subsystem would be performed at the same time to retain a portion of the log attributes rather than throwing an exception.

Worth considering would be whether the logging subsystem should swallow other exceptions thrown by the custom serialization functions.