Skip to content
Snippets Groups Projects

[Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration; Jami can't handle calls if the Android user enabled hardware acceleration

    • Closed Issue created by Elys @El4

    first title: Crash after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?)

    Alice: Android (EMUI 12) 20220615-01 Bob: Windows 10: Jami (beta-)Version 202206231612

    You make a video call Android -> Windows 10 ("username1" -> "username2").

    I think it's also related to the video codec H264? Probably not?

    You always have to exit Android and Windows 10 once you changed the settings: #763 (comment 37579)

    If you want to prevent a crash on Windows 10 you have to disable hardware acceleration and exit BOTH - the windows client AND the android client - and enter both apps again.

    Update: #763 (comment 37408)

    This is actually the main issue: #763 (comment 36675)

    It does not matter if you actually launch OBS-VirtualCam or not.

    If you select your video device "OBS-VirtualCam" but you disable Hardware Acceleration (using the video settings of the Jami client [Windows 10]) Jami will receive the Android call and crash as soon as you (the Windows 10 user) answer the call.

    • It does NOT happen if I select "ManyCam" and (also) disable hardware Acceleration. EDIT: Just reproduced a crash.
    • It does NOT happen if I select "OBS-VirtualCam" but ENABLE hardware acceleration.

    Here are the logs:

    [dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700]
    Edited

    Designs

      Child items ...

      2. Activity

      • Elys changed the description

        changed the description

      • Elys
        Elys @El4 ·
        Author

        Not sure if it related / caused by these steps or it just happend randomly.

        But if you have selected a virtual webcam (Manycam 4; but also Manycam 7,8) Jami can't select the right fps (The resolution might be displayed right but the frames per second is wrong). Normally if I start Jami the settings page show that Jami selects an (inactive) virtual cam.

      • Elys changed title from [Windows 10] Crash if you make a video Call Android -> Windows 10 to [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration

        changed title from [Windows 10] Crash if you make a video Call Android -> Windows 10 to [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration

      • Elys changed the description

        changed the description

      • Elys mentioned in issue jami-project#1453 (closed)

        mentioned in issue jami-project#1453 (closed)

      • Elys
        Elys @El4 ·
        Author

        I think you also get a crash if Jami selects the wrong fps (for example ManyCam is set to 30 fps and Jami only allows to select 60 fps)

        EDIT: Same issue if you use a "real" webcam and disable hardware acceleration:

        1. Make a video call (Android -> Windows 10)
        2. Now the Android user can see the windows user
        3. Not the Windows 10 user shares his screen
        4. Jami (Windows 10) crashes

        Windows 10: If you enable hardware acceleration you get a huge lag (a few seconds, a pixelated video) and it will also crash

        Edited by Elys
      • Elys
        Elys @El4 ·
        Author

        If I start a Jami I also get this error if I open the logs:

        [1658218242.476|18708|video_device_monitor.cpp:222  ] Failed to add device video=@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{27B05C2D-93DC-474A-A5DA-9BBA34CB2A9C}: invalid map key
[1658218242.481|18708|video_device_monitor.cpp:222  ] Failed to add device video=@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{9E2FBAC0-C951-4AA8-BFA9-4B196644964C}: invalid map key

        Full logs: This time disable Hardware Acceleration

         [rtp @ 000001A36BDE5400] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
[1658218795.053|11360|sipvoiplink.cpp   :1364 ] [INVITE:000001A36B3B4FE8] RX SIP method 6 (INFO)
[1658218795.055|11360|sipvoiplink.cpp   :1209 ] Rotate video 90 deg.
[1658218795.355| 5964|sipcall.cpp       :608  ] Sending video keyframe request via SIP INFO
[1658218795.398| 3020|media_encoder.cpp :938  ] H264 encoder setup: crf=33, maxrate=839 kbit/s, bufsize=419 kbit
[1658218795.566| 9984|accel.cpp         :208  ] -- Starting decoding init for cuda with default device.
[1658218795.648| 9984|accel.cpp         :182  ] Device type cuda successfully created.
[1658218795.649| 9984|accel.cpp         :215  ] -- Init passed for cuda with default device.
[1658218795.652| 9984|media_decoder.cpp :547  ] Using hardware decoding for h264 with nvdec
[1658218795.653| 9984|media_decoder.cpp :554  ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1658218795.654| 9984|video_receive_thread.cpp:276  ] [000001A376377240] Starting sink
[1658218795.654| 9984|sinkclient.cpp    :477  ] [Sink:000001A364B6C260] Started - size=1920x1080, mixer=No
[1658218795.655| 9984|video_receive_thread.cpp:203  ] [000001A376377240] Decoder configured, starting decoding
[1658218795.656| 9984|accel.cpp         :151  ] Found compatible hardware format for h264 decoder with nvdec
[1658218795.682| 9984|filter_transpose.cpp:31   ] Rotation set to 90
[1658218795.685| 9984|media_filter.cpp  :107  ] Filter graph initialized with: [in] transpose=2
[1658218795.687| 9984|sinkclient.cpp    :477  ] [Sink:000001A364B6C260] Started - size=1080x1920, mixer=No
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001A375AE8000] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
        Edited by Elys
      • Elys
        Elys @El4 ·
        Author

        I just used a "real" webcam (Hardware Acceleration is already disabled). I select my webcam instead of OBS-VirtualWebcam.

        Jami crashes after a few seconds. Same error logs.

        Restart Jami: Steps to reproduce:

        1. Start Jami (I launch jami as an admin; this issue does not change anything if I don't launch jami as an admin)
        2. Your "real" webcam is already selected (Hardware Acceleration is already disabled)
        3. Make a video call (Android -> Windows 10)
        4. Now the Windows 10 user shares his screen
        5. Jami (Windows 10) will crash
        6. After some seconds the call of Android user will also fail (but no crash)

        Even if I enable Hardware Acceleration Jami will crash a soon as I start to share my screen.

        Edited by Elys
      • Elys changed title from [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration to [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen

        changed title from [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration to [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen

      • Elys
        Elys @El4 ·
        Author

        I also got a crash after just answering a video call Android -> Windows 10.

        logs:

        [dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000002EE244BB200] real-time buffer [@device_pnp_\\?\usb#vid_145f&pid_0203&mi_00#6&2ad29b95&3&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (121% of size: 3041280 [rtbufsize parameter])! frame dropped!
        Edited by Elys
      • Elys
        Elys @El4 ·
        Author

        @sblin I'm sorry but at the moment Jami (Windows 10 client; beta version 202207191300) is unusable.

        [1658398191.128| 1100|sinkclient.cpp    :477  ] [Sink:00000180EBC003C0] Started - size=1280x720, mixer=No
[dshow @ 00000180E9781C00] real-time buffer [@device_pnp_\\?\root#image#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global] [video input] too full or near too full (90% of size: 3041280 [rtbufsize parameter])! frame dropped!

        I always get a crash randomly.

        This time:

        1. Make a video call (Android -> Windows 10)
        2. Now the Windows 10 user shares his screen
        3. This time no crash you can show your screen (Windows 10 user)
        4. Now the Windows 10 user stops to share his screen
        5. Jami (Windows 10) will crash

        BTW: Still this issue: ( jami-project#1405 (closed) )

        Next step

        This time I disabled Hardware Acceleration and used "OBS-VirtualCam" (1360x769; 30 fps). More stable but as soon as I stop to share my screen (Windows 10; using the "Share Screen" option of Jami) Jami will also crash.

        Edited by Elys
      • Elys mentioned in issue jami-project#1449 (closed)

        mentioned in issue jami-project#1449 (closed)

      • Elys
        Elys @El4 ·
        Author

        Jami (Windows 10) will always crash (does not matter if I enable or disable Hardware Acceleration) if I launch the OBS-VirtualCam (so you don't see the preview (Url: https://www.kiloview.com/en/wp-content/uploads/2021/08/obs-virtual-camera-image-cover-600.jpg) anymore, but the "real" screen of your pc)

        EDIT: No issues if you make a call without a camera / virtual cam - just audio call.

        Edited by Elys
      • Elys changed title from [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen

        changed title from [Windows 10] Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen

      • Elys
        Elys @El4 ·
        Author

        changing the video codec didn't help but I use h.264/AVC

      • Elys changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen

        changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" and DISABLE Hardware Acceleration or after you share your screen to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen

      • Elys changed the description

        changed the description

      • Elys
        Elys @El4 ·
        Author

        Using ManyCam 7: If I enable Hardware Acceleration I never got a crash, even if I use the "screenshare option" of Jami after I use "ManyCam Virtual Webcam".

        However -Jami can't select 30 fps (always just 60fps) although ManyCam is set to 30 fps (#747 (closed)) and the Android user (call Windows 10 -> Android) will get a huge video lag of the screen content of the Windows 10 user if the Windows 10 user enables Hardware Acceleration (#775 (closed))

      • Elys changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen (just OBS?)

        changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen (just OBS?)

      • Elys
        Elys @El4 ·
        Author

        I just used OBS-VirtualCam to record and send a video (Jami account 1 (Windows 10 user) -> Jami account2 (Android user). No issues.

        I can even make a video call.

        However - as soon as I share my screen using the Jami "share screen" option Jami (Windows 10) crashes.

        EDIT: It seems it does not matter if I make a call Windows 10 -> Android OR Android -> Windows 10

        Always same result (just the windows 10 client crashes)

        Edited by Elys
      • Elys
        Elys @El4 ·
        Author

        Sometimes it is possible to make a video call shortly; using ManyCam (not launched; so you just see the preview)

        during a video call:

        • Windows 10: You can see the preview of ManyCam (Url: https://i.stack.imgur.com/m4AH7.jpg ;because I did not launch ManyCam)
        • the Windows 10 user now shares his screen using the "share screen" option of Jami (sometimes you already get a crash)
        • Now the Windows 10 user stops to share his screen (sometimes you already get a crash)
        • Now the Windows 10 user still shows the preview of ManyCam
        • Now the Windows 10 user shares his screen again
        • Now the Windows 10 user stops to share his screen
        • Windows 10 crash
        Edited by Elys
      • Elys mentioned in issue jami-daemon#743 (closed)

        mentioned in issue jami-daemon#743 (closed)

      • Elys mentioned in issue #795

        mentioned in issue #795

      • Elys mentioned in issue jami-daemon#755 (closed)

        mentioned in issue jami-daemon#755 (closed)

      • Elys changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen (just OBS?) to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you shared your screen twice

        changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you share your screen (just OBS?) to [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you shared your screen twice

      • Elys changed the description

        changed the description

      • Elys changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you shared your screen twice to [Windows 10] Video-call: Crash if after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?)

        changed title from [Windows 10] Video-call: Crash if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration or after you shared your screen twice to [Windows 10] Video-call: Crash if after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?)

      • Elys changed title from [Windows 10] Video-call: Crash if after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?) to [Windows 10] Video-call: Crash after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?)

        changed title from [Windows 10] Video-call: Crash if after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?) to [Windows 10] Video-call: Crash after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?)

      • Elys
        Elys @El4 ·
        Author

        I think this crash also happens if you follow these steps (this time I use a "real" webcam)

        Make a video call: Windows 10-> Android

        Android: accept call in portrait mode

        Android: Now rotate the phone so you can see the Windows 10 user in landscape mode

        Windows 10: After a few seconds you get a crash (Android won't crash; and once you open Jami (Windows 10) again you can make calls after 30 seconds)

      • Elys changed the description

        changed the description

      • Elys
        Elys @El4 ·
        Author

        (all devices select video codec H.264/AVC and VP8)

        If both peers - the Android user AND the Windows 10 user ENable hardware acceleration I never got a crash.

        • Just Windows 10: But even if I select 720p (#775 (closed)) I get a video lag if enable hardware acceleration (the video of the real camera lags and also the option of Jami to share my screen).
        • If you just disable hardware acceleration on Android you see the caller of the phone pixellated but after the Windows 10 user shared the screen (twice), Windows 10 will crash
        • If both peers disable hardware acceleration after the Windows 10 user stops to share his screen Jami will crash

        Maybe you can also try out many people in a conference (and in the future Swarm-calls) using different settings when it comes to hardware acceleration.

        EDIT: I think this crash also happens randomly and/or if you don't exit Jami (both apps?) after you applied the settings and/or enabled video again. So you have to change the settings, exit Jami and enter Jami again.

        Edited by Elys
      • Elys changed title from [Windows 10] Video-call: Crash after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?) to [Windows 10] Video-call: Crash if both peers don't enable hardware acceleration

        changed title from [Windows 10] Video-call: Crash after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?) to [Windows 10] Video-call: Crash if both peers don't enable hardware acceleration

      • Elys changed the description

        changed the description

      • Elys changed title from [Windows 10] Video-call: Crash if both peers don't enable hardware acceleration to [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android users;) don't enable hardware acceleration

        changed title from [Windows 10] Video-call: Crash if both peers don't enable hardware acceleration to [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android users;) don't enable hardware acceleration

      • Elys changed title from [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android users;) don't enable hardware acceleration to [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration

        changed title from [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android users;) don't enable hardware acceleration to [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration

      • Elys mentioned in issue jami-project#1309 (closed)

        mentioned in issue jami-project#1309 (closed)

        • Elys
          Elys @El4 ·
          Author

          @atraczyk So I've done some testing and now I can describe the following issue:

          I've always used the beta newest version of the Android version of Jami

          but I used different old version of the Jami Windows 10 client:

          • If I used Jami Version 202010151812 I never had any issues (no issues)

          Now I've discovered the following issue [always using newest beta version of Jami on Android - but older versions of the Windows 10 client]:

          I mostly never exit Jami on Android; I just exit Windows 10 (or open again if I get a crash)

          calls always "username1" -> "username2"

          Since (Windows 10) Jami 202010160957: (or 202011191640?) Even if I just open Jami (Windows 10) I get a crash if one contact in my contact list (the Android user) enabled harware acceleration (generally / before I launch Jami on Windows 10). So I never send any text messages / attachments and never make a call.

          (Sometimes you have to exit Jami (Windows 10) and open Jami again to reproduce a crash (without any video call) But very often Jami will crash after ten seconds if just the Android user enabled hardware acceleration)

          It does NOT matter if the Windows 10 client enabled or disabled hardware acceleration.

          • If just the Android client enabled VP8 (and hardware acceleration), but the Windows 10 client uses vp8 and h264 I get a crash
          • I tried different video codecs but always reproduced a crash if I make a video call Android (hardware acceleration enabled) -> Windows 10
          • Even if Windows 10 and Android use completely different video codecs but just the Android client enabled hardware accleration the windows 10 client of Jami will crash after a few seconds (only older versions of Jami), even if you never send any message or make a video call
          • Even if you didn't reproduced a crash as soon as you make a video call Jami will crash (does not matter which video codec you use). If you use new version of Jami you have to follow these steps: #763 (comment 36675) or #763 (comment 37408)

          As mentioned older versions of Jami (Windows 10; 202010160957) crashed even if I didn't make any video call but just the Android contact in the contact list enabled hardware acceleration

        • Elys
          Elys @El4 ·
          Author

          This time I used the newest version of Jami (202209161341)

          If I disable hardware acceleration on Android but enable hardware acceleration on Windows 10 (using OBS-VirtualCam; Full-HD, 30fps) I get a crash if make a video call.

          No crash if I disabled hardware acceleration on Android and Windows 10?

          Edit: (Android: hardware acceleration already disabled)

          If you want to prevent a crash on Windows 10 you have to disable hardware acceleration and exit BOTH - the windows client AND the android client - and enter both apps again.

          • If you just disable hardware acceleration on Windows and make a call afterwards (no exit) you still get a crash
          • If you just disable hardware acceleration on Windows and just exit Windows but not Android you still get a crash
          Edited by Elys
        • Please register or sign in to reply
      • Elys changed title from [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration to [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration; Jami can't handle calls if the Android user enabled hardware acceleration

        changed title from [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration to [Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration; Jami can't handle calls if the Android user enabled hardware acceleration

      • Elys changed the description

        changed the description

      • Elys changed the description

        changed the description

      • Elys mentioned in issue jami-client-android#1125 (closed)

        mentioned in issue jami-client-android#1125 (closed)

      • Elys
        Elys @El4 ·
        Author

        @atraczyk Did this patch https://review.jami.net/c/jami-client-qt/+/22565 also fix this issue? I think I can't reproduce anymore.

        Can someone still reproduce? If no we can close.

        Edited by Elys
      • Sébastien Blin
        Sébastien Blin @sblin ·
        Owner

        I can't reproduce

      • Sébastien Blin closed

        closed

      • Elys mentioned in issue #1242

        mentioned in issue #1242

      Please register or sign in to reply