Connect socket crash after close soket.

[SGaist]

Did you properly allocate socket ?

[senmx]

@SGaist The socket object is not destroyed when it is closed, and the socket object is still the original when it is reconnected. It would be nice if can locate the code line.

[SGaist]

You are using deleteLater once it's called, the object will be deleted and you will have a dangling pointer.

In any case, you do not answer my question: is socket properly allocated before you use it ?

[senmx]

@SGaist Does it mean this, only new once when the app starts.

socket = new QTcpSocket();
timeoutTimer = new QTimer();
timeoutTimer->setSingleShot(true);
connect(timeoutTimer, &QTimer::timeout, this, &SocketManager::connectionTimeout);
connect(socket, &QTcpSocket::disconnected, this, &SocketManager::disconnected);

[Christian Ehrlicher]

@senmx said in Connect socket crash after close soket.:

only new once when the app starts.

But when you delete it during the runtime then you will get a dangling pointer as @SGaist already pointed out.

[senmx]

@Christian-Ehrlicher I do not destroy the socket object when logout, just disconnect.

[Christian Ehrlicher]

@senmx said in Connect socket crash after close soket.:

just disconnect.

Not according to your (incomplete) code snippet:

connect(socket,SIGNAL(disconnected()),socket,SLOT(deleteLater()));

[senmx]

@Christian-Ehrlicher According to SGaist's reply, this sentence has been removed.Then I will close this question and ask another question again.

[Christian Ehrlicher]

Please show a fully working example - we don't know what you're doing when you only post misc fragments of your code.

[senmx]

@Christian-Ehrlicher Thanks. I asked another question, please take a look.
https://forum.qt.io/topic/122204/how-to-get-detailed-errors-from-libc-so-to-the-app-code-line