Thanks Nick for the response. Actually, after multiple round of testing during load condition I am still hitting this issue so at the end I have to disable GFX for now and go ahead but that has a different disadvantage. So still this issue is open for me, maybe upgrading with freerdp 3.x can help but haven't tested with that.
-Dilip On Sun, Sep 7, 2025 at 6:00 AM Nick Couchman <[email protected]> wrote: > On Sun, Aug 17, 2025 at 5:34 AM Dilip Modi <[email protected]> > wrote: > >> Thanks Nick. >> I could not able to fix this issue at the moment and need your help to >> fix this. How we can avoid this crash during load condition and while >> cleanup is happening? >> >> > I'm not sure I understand. In the section below you say: > > >> *Analysis and Troubleshooting Steps Taken* >>>> >>>> Our investigation points towards a memory corruption issue, likely a >>>> race condition exposed by the high rate of connection setup and teardown. >>>> The logs around the time of the crash show many "Handshake failed, >>>> 'connect' instruction was not received" errors, indicating this high churn. >>>> >>>> We have progressively identified and fixed several bugs: >>>> >>>> 1. *Incorrect Cleanup Order:* Initially, we found >>>> that freerdp_disconnect() was called before gdi_free(), which we >>>> corrected. >>>> >>>> >>>> > It sounds to me like you have located and corrected the issue. I'm asking > if you can submit a Jira issue and a pull request for the fix to this issue > so that we can merge it in? > > -Nick > -- This communication (including any attachments) is intended for the sole use of the intended recipient and may contain confidential, non-public, and/or privileged material. Use, distribution, or reproduction of this communication by unintended recipients is not authorized. If you received this communication in error, please immediately notify the sender and then delete all copies of this communication from your system.
