Skip to content
Snippets Groups Projects
New look: Off

High CPU usage and high data usage

    • Closed Issue created by ovari @ovari

    Bug report

    • Platform: Linux
    • OS version: Linux Mint 22 Cinnamon
    • Jami version: 202408241534
    • Distribution channel : Jami.net
    • Can you reproduce the bug: every time Jami is opened

    Steps to reproduce (STR)

    1. Open Jami
    2. After a few seconds:
      (a) CPU usage > 10% and computer fan starts (normally the fan is off)
      (b) Network (Internet): download (receiving) > 300KiB/s and upload (sending) > 300KiB (normally in bytes/s)
      (c) Data usage after a few minutes > 100MiB

    Causes might be

    1. A swarm has had members leave (i.e. left).
    2. Jami has not been offline for over 24 hours and there git conversation has become corrupted?

    Actual result

    1. High CPU usage
    2. High data usage

    Possible solution

    Wait for a newer Jami version to be released as it may resolve this issue as members in the swarm are using a newer, yet to be released, version of Jami that has some improvements.

    Terminal

    jami -d

    Red

    [device REDACTED] no response from DHT to ICE request.
    [1728101387.600|8437|conversation_module.cpp :675 ] [Account REDACTED] Relaunch sync with REDACTED for REDACTED
[1728101387.120|8237|message_engine.cpp      :150 ] [message 7365877044217913] Message sent: success
[1728101387.120|8237|message_engine.cpp      :169 ] [message 7365877044217913] Status changed to SENT
[1728101387.120|8237|message_engine.cpp      :150 ] [message 8492960469249007] Message sent: success
[1728101387.120|8237|message_engine.cpp      :169 ] [message 8492960469249007] Status changed to SENT
[1728101387.161|8239|message_engine.cpp      :119 ] [message 977972225044266] Retry sending
[1728101387.161|8239|message_engine.cpp      :150 ] [message 977972225044266] Message sent: failure
[1728101387.161|8239|message_engine.cpp      :193 ] [message 977972225044266] Status changed to IDLE
[1728101387.161|8239|message_engine.cpp      :119 ] [message 4892399785142589] Retry sending
[1728101387.161|8239|message_engine.cpp      :150 ] [message 4892399785142589] Message sent: failure
[1728101387.161|8239|message_engine.cpp      :193 ] [message 4892399785142589] Status changed to IDLE
[1728101387.161|8239|message_engine.cpp      :119 ] [message 6036217879396983] Retry sending
[1728101387.161|8239|message_engine.cpp      :119 ] [message 3096904135415803] Retry sending
[1728101387.161|8239|message_engine.cpp      :119 ] [message 2237476980433834] Retry sending
[1728101387.162|8239|message_engine.cpp      :150 ] [message 2237476980433834] Message sent: failure
[1728101387.162|8239|message_engine.cpp      :193 ] [message 2237476980433834] Status changed to IDLE
[1728101387.162|8239|jamiaccount.cpp         :3494] [Account REDACTED] Request SIP connection to peer REDACTED on device REDACTED
[1728101387.162|8239|jamiaccount.cpp         :3517] [Account REDACTED] Already connecting to REDACTED
[1728101387.162|8239|message_engine.cpp      :119 ] [message 5004831448666648] Retry sending
[1728101387.162|8239|message_engine.cpp      :150 ] [message 5004831448666648] Message sent: failure
[1728101387.162|8239|message_engine.cpp      :193 ] [message 5004831448666648] Status changed to IDLE
[1728101387.162|8239|jamiaccount.cpp         :3494] [Account REDACTED] Request SIP connection to peer REDACTED on device REDACTED
[1728101387.162|8239|jamiaccount.cpp         :3517] [Account REDACTED] Already connecting to REDACTED
[1728101387.162|8239|message_engine.cpp      :119 ] [message 1911187485824494] Retry sending
[1728101387.162|8239|message_engine.cpp      :150 ] [message 1911187485824494] Message sent: failure
[1728101387.162|8239|message_engine.cpp      :193 ] [message 1911187485824494] Status changed to IDLE
[1728101387.162|8239|jamiaccount.cpp         :3494] [Account REDACTED] Request SIP connection to peer REDACTED on device REDACTED
[1728101387.162|8239|jamiaccount.cpp         :3517] [Account REDACTED] Already connecting to REDACTED
[1728101387.166|8354|sipaccountbase.cpp      :283 ] Text message received from REDACTED, 1 part(s)
[1728101387.166|8431|conversation_module.cpp :580 ] [Account REDACTED] fetch commits from REDACTED, for REDACTED, commit 806f4dac97610c5b0fd27ce4be6a4329d1f257a8
[1728101387.167|8431|conversationrepository.cpp:2163] [conv REDACTED] Couldn't init revwalker
[1728101387.168|8431|conversation_module.cpp :669 ] [Account REDACTED] Could not fetch new commit from REDACTED for REDACTED, other peer may be disconnected

    More information

    Please advise if you require more verbose and/or unredacted terminal output.

    Thank you

    Edited

    Designs

      Child items ...

      2. Activity

      • ovari changed the description

        changed the description

      • ovari closed

        closed

        • ovari
          ovari @ovari ·
          Author

          Formatted disk, reinstalled operating system, installed Jami and restored Jami from back up. High CPU usage (13% CPU) and data usage is occurring again when Jami is running. Noticeable as the CPU fan operates when Jami is open; otherwise, the CPU fan never turns on.

          Unfortunately, this situation makes it very difficult to have Jami running.

          Edited by ovari
        • François-Simon Fauteux-Chapleau
          François-Simon Fauteux-Chapleau @ffauteux-chapleau ·
          Developer

          We've noticed this bug too and I think I was able to find the cause. There seems to be a bug in the algorithm used to synchronize data between swarm members that can lead to large amounts of (unnecessary) network traffic in some situations. Unfortunately, it looks like the "Collaborative editor" swarm got into one of these situations, which is why you're experiencing this issue. I need to do more tests but if the problem is what I think it is, then it shouldn't be too hard to solve and we'll hopefully have a fix released soon.

          Edited by François-Simon Fauteux-Chapleau
        • ovari
          ovari @ovari ·
          Author

          Yes, the cause seems to be the "Collaborative editor" swarm. Thank you for the developers accepting invitations to the group swarm so that problem can be discovered and reproduced.

          Will a unit test be added for the fix too?

          Thank you once again

        • Please register or sign in to reply
      • ovari reopened

        reopened

      • François-Simon Fauteux-Chapleau assigned to @ahatziiliou and @ffauteux-chapleau

        assigned to @ahatziiliou and @ffauteux-chapleau

      • François-Simon Fauteux-Chapleau added severitycritical sprintin progress typebug labels

        added severitycritical sprintin progress typebug labels

        • Lanius-collaris
          Lanius-collaris @Lanius-collaris ·

          If percentage of UDP traffic is high (Not likely), it may be DoS on DHT. You can enable DHT proxy and see if the issue disappears.

          [device REDACTED] no response from DHT to ICE request.

          It's very common.

          :thinking:perf tool has support for flame graphs. You can use it record data, then run perf script report flamegraph to generate a flamegraph.html.

          Sorry for noise.

          Edited by Lanius-collaris
        • ovari
          ovari @ovari ·
          Author

          Thank you for reading and commenting. Noise in good faith is always welcome.

        • Please register or sign in to reply
      • ovari
        ovari @ovari ·
        Author

        https://review.jami.net/c/jami-daemon/+/29217

      • François-Simon Fauteux-Chapleau mentioned in commit jami-daemon@fc50f5d6

        mentioned in commit jami-daemon@fc50f5d6

        • ovari
          ovari @ovari ·
          Author

          Can you please advise an ETA for releases of Jami for Android, Linux and Windows that contain the merge https://review.jami.net/c/jami-daemon/+/29217 patch? Thank you

        • François-Simon Fauteux-Chapleau
          François-Simon Fauteux-Chapleau @ffauteux-chapleau ·
          Developer

          I think there's an Android release planned for tonight or tomorrow. For Linux I'm planning to do one once the patch https://review.jami.net/c/dhtnet/+/26442 is merged (hopefully tomorrow). I'm not sure about Windows.

          By the way, just to make sure there's no misunderstanding: the patch you link to limits the amount of outgoing traffic generated by Jami, but it can't prevent non-patched instances of Jami from generating an excessive amount of incoming traffic. Concretely, this means that even if you update Jami as soon as the new release becomes available, the issue with the "Collaborative editor" swarm will probably persist for a little while (until the other members also upgrade their version of Jami).

        • ovari
          ovari @ovari ·
          Author

          Thank you for your comment.

          We are planning to have a “group conversation” swarm on the weekend with members that have Android, Linux and Windows operating systems to test the fix. We can advise the members in the group conversation to update their Jami edition before we test.

          Does Android and Windows Jami clients also require the https://review.jami.net/c/dhtnet/+/26442 patch?

          Thank you once again.

        • François-Simon Fauteux-Chapleau
          François-Simon Fauteux-Chapleau @ffauteux-chapleau ·
          Developer

          The https://review.jami.net/c/dhtnet/+/26442 patch will hopefully improve connection reliability on all platforms, but it is unrelated to the swarm issue (and therefore not needed to fix it).

          Note that the high CPU/data usage issue you've been experiencing does not occur in all swarms. In fact, the "Collaborative editor" swarm is the only instance of this bug that I'm aware of. This means that if you create a new swarm to do your weekend test, then you probably won't be able to reproduce the bug, regardless of the version of Jami you're using. (If you do manage to reproduce the issue in a new swarm, then please let me know; I would be very interested in having more information about the conditions that trigger this bug.)

        • ovari
          ovari @ovari ·
          Author

          I would be very interested in having more information about the conditions that trigger this bug.)

          Unfortunately, issue occurred in group conversation today with 4 devices:

          1. Jami 202411011335, Linux Mint 22 Cinnamon
            Jami 202411011335, Linux Mint 22 Cinnamon
          2. Jami beta 202411041251, Windows 10
          3. Jami TODO, Windows 10
          4. Jami Astarte 20241112 01, Android 14 phone, Samsung Galaxy 55
          Edited by ovari
        • François-Simon Fauteux-Chapleau
          François-Simon Fauteux-Chapleau @ffauteux-chapleau ·
          Developer

          Can you give me more details about what happened exactly? The image shows high memory usage but the CPU looks normal and there's no information about network data.

          1. Was CPU usage abnormally high before you took the screenshot?
          2. How about network/data usage?
          3. Did the logs look similar to what we were seeing in the original issue (i.e. lots of Retry sending and Message sent: failure)?
          4. Do you see this message in the logs (with different device/commit hashes of course)?
          Successfully fetched from device 8fbe9ed53d61f0813d4018bbd5133afd84f3a3729f9379a15e72477fc040c5a0 but didn't receive expected commit 3761853b81942eea4c83da002ddf399037d96b05

          If it's possible for you to find out what version of Jami was used on the second Windows 10 device and on the Android phone, that'd be useful to know as well.

        • ovari
          ovari @ovari ·
          Author

          Edit: Moved text in strikethrough to #1882 (closed)

          1. Collaborative editor group conversation has `4a03878dac4655b55baef406294b5462e14322a7` in `Invited` (greyed) state, but unable to kick/remove member. 1. `4a03878dac4655b55baef406294b5462e14322a7` is not in 1:1 conversation as we both have selected `Leave conversation` 
          [1731405672.935|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405672.940|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405673.937|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405673.939|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405674.944|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405674.950|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405675.910|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405675.914|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405676.923|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405676.933|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405677.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405677.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405678.920|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405678.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405679.904|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405679.910|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405680.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405680.931|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405681.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405681.935|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405682.919|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405682.924|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405683.919|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405683.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405684.920|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405684.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405685.920|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405685.924|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405686.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405686.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405687.924|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405687.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405688.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405688.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405689.920|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405689.924|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405690.928|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405690.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405691.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405691.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405692.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405692.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405693.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405693.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405694.924|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405694.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405695.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405695.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405696.920|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405696.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405697.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405697.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405698.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405698.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405699.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405699.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405700.909|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405700.914|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405701.920|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405701.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405702.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405702.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405703.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405703.928|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405704.919|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405704.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405705.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405705.936|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405706.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405706.928|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405707.919|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405707.923|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405708.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405708.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405709.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405709.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405710.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405710.934|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405711.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405711.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405712.925|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405712.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405713.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405713.929|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405714.926|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0
[1731405714.930|2060|namedirectory.cpp       :178 ] Address lookup for 4a03878dac4655b55baef406294b5462e14322a7 failed with code=0

          If it's possible for you to find out what version of Jami was used on the second Windows 10 device and on the Android phone, that'd be useful to know as well.

          Have sent messages to people with Windows 10 computer and Android phone devices asking for Jami versions when then were online. Unfortunately no answer.

          Person with Android phone is not connected to the Jami network at the moment.

          Edited by ovari
        • François-Simon Fauteux-Chapleau
          François-Simon Fauteux-Chapleau @ffauteux-chapleau ·
          Developer

          @ovari Were you also seeing address lookup failures in the 4-device conversation mentioned in comment #1851 (comment 53733)? If not, then please open a separate issue for this; putting several unrelated bugs in the same GitLab issue makes it harder for developers to keep track of them.

          I'd still be interested in answers to questions 1-4 in my previous comment. Right now it's not clear to me if the issue you had in the 4-device conversation is the same as the one we fixed (or thought we had fixed) last month.

          Edited by François-Simon Fauteux-Chapleau
        • ovari
          ovari @ovari ·
          Author
          1. Was CPU usage abnormally high before you took the screenshot?

          It was higher than the screenshot. There is a delay before the screenshot happened.

          1. How about network/data usage?

          On the weekend there was a group audio call. After the call a lot of data was used. Closing Jami considerably slowed down the data usage.

          1. Did the logs look similar to what we were seeing in the original issue (i.e. lots of Retry sending and Message sent: failure)?

          Sent debug file to you via Jami.

          1. Do you see this message in the logs (with different device/commit hashes of course)?

          Unable to see that; however, there are failures.

          [1731457589.684|25227] Skipping OCSP verification REDACTED: request failed
[1731457589.966|25252|conversation_module.cpp :1362] Clone failed. Re-clone in 1280s
        • François-Simon Fauteux-Chapleau
          François-Simon Fauteux-Chapleau @ffauteux-chapleau ·
          Developer

          Thanks for the answers. I don't see anything in the debug file that seems related to the issue, but that was to be expected if you generated it after the fact. I was hoping that you had saved the logs (i.e. the output of jami -d) that were produced while the problem was occurring, but if you didn't, then I guess we'll have to wait until you (or someone else) can reproduce the issue to get more information.

        • Please register or sign in to reply
      • ovari mentioned in issue jami-client-android#1094

        mentioned in issue jami-client-android#1094

      • ovari closed

        closed

      • François-Simon Fauteux-Chapleau added sprintdone label and removed sprintin progress label

        added sprintdone label and removed sprintin progress label

      • ovari reopened

        reopened

      • ovari closed

        closed

      • ovari mentioned in issue #1894

        mentioned in issue #1894

      Please register or sign in to reply