microsoft-identity-device-broker: OOM exception for Java heap

[xaner4]

Hi, Does anyone else need to restart microsoft-identity-device-broker.service every few hours?
I see in the journalctl logs that there's a lot of OOM errors in the java heap space.

Jul 01 16:45:30 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBus Worker Thread-1" java.lang.OutOfMemoryError: Java heap space
Jul 01 16:54:08 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBus Worker Thread-2" java.lang.OutOfMemoryError: Java heap space
Jul 01 16:57:57 fedora microsoft-identity-device-broker[816654]: Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "DBus Worker Thread-7"
Jul 01 16:57:58 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBus Worker Thread-6" java.lang.OutOfMemoryError: Java heap space
Jul 01 16:57:58 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBus Worker Thread-5" java.lang.OutOfMemoryError: Java heap space
Jul 01 17:00:47 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBus Worker Thread-4" java.lang.OutOfMemoryError: Java heap space
Jul 01 17:04:22 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBusConnection" java.lang.OutOfMemoryError: Java heap space
Jul 01 17:04:45 fedora microsoft-identity-device-broker[816654]: Exception in thread "pool-1-thread-1" java.lang.OutOfMemoryError: Java heap space
Jul 01 17:04:49 fedora microsoft-identity-device-broker[816654]: Exception in thread "DBus Worker Thread-8" java.lang.OutOfMemoryError: Java heap space

The /usr/lib/systemd/system/microsoft-identity-device-broker.service file sets -Xmx to 128m, which is probably a little small, but this was the default

Environment="JAVA_OPTS=-Xmx128m -Xss256k -XX:+UseParallelGC -XX:ParallelGCThreads=1"

I also thinks that the it's a little weird that it is using both -XX:+UseParallelGC and -XX:ParallelGCThreads=1, Doesn't that contradict each other?

Would it be enough to increase the xmx to 512m or something like this or is there a memory leak in that service maybe?