0004356: Client crashes if connecting to local server with internal browser if already on same server

Notes
(0023871) Kaminsky (developer) 2024-07-31 20:16	Here's a merge request to fix the crash:'https://foss.heptapod.net/zandronum/zandronum-stable/-/merge_requests/148 [^]'

(0023873) Kaminsky (developer) 2024-07-31 21:23	This has been pushed into the main repository:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/3d0b30bd60c102f3ee701237ff26b863258a5015 [^]'

(0023876) unknownna (updater) 2024-08-01 06:48	It fixed the crash it seems, but I still sometimes get kicked for missing too many packets. And when it attempts to connect, it looks very frozen until you're suddenly on the server again, but maybe I'm being picky here. I suspect the packet loss kick might be caused by this issue, which was strangely closed without being fixed:'https://zandronum.com/tracker/view.php?id=2618 [^]'

(0024101) unknownna (updater) 2024-10-26 04:47 edited on: 2024-10-26 04:54	Since the crash was fixed, I'll mark this as resolved. The other ticket has to be re-opened since it still happens and probably causes the client to get kicked for missed packets. Quote from unknownna And when it attempts to connect, it looks very frozen until you're suddenly on the server again, but maybe I'm being picky here. It would be better if the client was put in the full console and "viewactive = false" when connecting. I'll make a note of it and maybe report it sometime in the future. Edit: Quote from unknownna The other ticket has to be re-opened since it still happens and probably causes the client to get kicked for missed packets. Actually, it didn't seem to happen in the latest 3.2 build I tested, so I'll not re-open it until I notice it again.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue Community Support

This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.

Supporters:

No one explicitly supports this issue yet.

Opponents:

No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2024-07-31 17:43	unknownna	New Issue
2024-07-31 17:43	unknownna	File Added: CrashReport.zip
2024-07-31 20:16	Kaminsky	Note Added: 0023871
2024-07-31 20:16	Kaminsky	Assigned To	=> Kaminsky
2024-07-31 20:16	Kaminsky	Status	new => needs review
2024-07-31 20:16	Kaminsky	Product Version	=> 3.2
2024-07-31 20:16	Kaminsky	Target Version	=> 3.2
2024-07-31 21:23	Kaminsky	Note Added: 0023873
2024-07-31 21:23	Kaminsky	Status	needs review => needs testing
2024-08-01 06:48	unknownna	Note Added: 0023876
2024-08-01 06:48	unknownna	Status	needs testing => feedback
2024-10-26 04:47	unknownna	Note Added: 0024101
2024-10-26 04:47	unknownna	Status	feedback => assigned
2024-10-26 04:47	unknownna	Status	assigned => resolved
2024-10-26 04:47	unknownna	Fixed in Version	=> 3.2
2024-10-26 04:47	unknownna	Resolution	open => fixed
2024-10-26 04:52	unknownna	Status	resolved => feedback
2024-10-26 04:52	unknownna	Resolution	fixed => reopened
2024-10-26 04:54	unknownna	Note Edited: 0024101	View Revisions
2024-10-26 04:54	unknownna	Status	feedback => resolved
2024-10-26 04:54	unknownna	Resolution	reopened => fixed

Relationships