Problem on womegle (omegle clone)

[duchnoun]

I'm excited to share a project I've been passionately working on: Womegle, a clone of the popular random chat platform Omegle, developed using PHP and FrankenPHP. Womegle aims to recreate the spontaneous and intriguing experience of Omegle, facilitating anonymous text and video chats between users.

Project Background
The core idea behind Womegle is to leverage the simplicity and flexibility of PHP, enhanced by the capabilities of FrankenPHP, to create a lightweight and efficient random chat platform. It's designed to be easy to set up and use, with a focus on real-time communication.

Current Challenges
While I'm thrilled with the progress, there are a couple of technical hurdles I'm currently facing, and I would greatly appreciate any insights or assistance from the community:

Memory Leak Issue:

I've noticed a persistent memory leak in the application. Despite my efforts to optimize the code and manage resources efficiently, this leak continues to affect the performance and scalability of Womegle.
If anyone has experience dealing with memory leaks in PHP/FrankenPHP environments, your guidance would be invaluable. Tips on debugging, profiling, or specific PHP memory management practices would be greatly appreciated.
WebRTC Connection Issues:

Another challenge is the occasional failure in establishing WebRTC connections. This issue is intermittent but critical, as it hinders the core functionality of the platform.
Insights into common pitfalls with WebRTC, especially in the context of PHP-based applications, or diagnostic strategies to pinpoint and resolve these connection issues would be incredibly helpful.