Sebastian Scheibner

From the code I can't see how this can happen, there's a `containsSession` check before loading the session. A verbose log might show more details on what's going on here.

Not much to go on here. Please run the signal-cli command with `-vv` parameter to get more detailed logging.

Thanks for the log. It's possible that inefficient queries cause slow down, but I don't see that consuming 100% CPU. Suspicious is the following receive thread log entry: `Reading cached...

@gwillem in your case signal-cli seems to still be catching up with old messages from a month ago. Is it still at 100% cpu when all messages have been received?

@gwillem you could reregister the account, that should clear the message queue on the server. `signal-cli register --reregister` If you have set a pin (`signal-cli setPin`) that should work without...

The logic for loading the native library is implemented here in libsignal-client: https://github.com/signalapp/libsignal/blob/main/java/shared/java/org/signal/libsignal/internal/Native.java#L70 It first tries to load a library with an architecture suffix (_amd64) and then tries without the...

Those have some additional testing APIs, they're not used by signal-cli. https://github.com/signalapp/libsignal?tab=readme-ov-file#maven-central

The first error indicates that this is a problem with the native libsignal-client library. So by default the tests only work on platform supported by the libsignal-client library (not arm...

Yeah, there have been changes in libsignal-client, so now the native library is required for the tests

Storage of messages and media could be implemented, but probably not in the near future.