Open M4LuZ opened 7 months ago
Did a bit of tracing on dev-dev
and it turns out that the memory leak is in the Transport
destructor.
Apparently while waitForReadyRead
in Transport.php
is supposed to immediately return when disconnected or in blocking mode it goes through the do {...} while(@stream_select(...))
loop indefinitely.
Adding blocking=0
to the query string appears to break the loop, timeout does not.
I moved $this->disconnect();
in Transport.php destructor and the issue seems to be fixed?
public function __destruct()
{
+ $this->disconnect();
if ($this->adapter instanceof Adapter) {
$this->adapter->__destruct();
}
-
- $this->disconnect();
}
Hi @toster234 ,
sorry for the late reply. Can confirm that this solves the issue for me. A quick check with the text viewer worked OK (the other two HTML / JSON appear to be broken and are the next ticket to be raised).
Hi y'all,
I'm currently working on a refresh of the integration of ts3phpframework into the LanSuite Lanparty CMS . I'm facing an apparent regression between 1.1.35 and 1.2.1 causing an out-of-memory error ultimately thrown in StringHelper.php Line 211
Story so far
^1.2
, thus ending on1.2.1
as version usedserveradmin
for the query connectionREADME.md
$TS3PHPFramework->factory($uri)
; I ran into out-of-memory errorsdev-master
(!)dev-master
is apparently outdated after renaming, on state of1.1.35
and as far as text goes not really compatible with PHP 8.2.1.2.1
has the issue reappearing immediately, same ondev-dev
(duh!)I saw that this issue was apparently already noticed and supposed to be fixed in #195 but somehow this appears not to be the case? So would be greatly appreciated to get some feedback on that.
Environment