Driving Client Crash (TinTin++)

I have been having an interesting problem over the past several months where occasionally while driving and coming to a halt, shortly afterwards the TinTin++ client will crash. After some puzzling about I've determined this is due to a #Zap function being called by the client which is usually triggered by the user deliberately (this is usually like a kill function to stop running sessions one by one by name). This is the code for that function in TinTin (hopefully my code tags don't break everything):

DO_COMMAND(do_zap)
{
	struct session *sesptr;
	char arg1[BUFFER_SIZE];
	push_call("do_zap(%p,%p)",ses,arg);
	sub_arg_in_braces(ses, arg, arg1, GET_ALL, SUB_VAR

This is the relevant code for TinTin++ from their Github, for the #zap function to kill active sessions.

I've combed through the raw client logs of 20 or so instances of this #zap being triggered while driving, and there is nothing obvious to me that is being received that could trigger some niche command or client crash (no strange characters or pseudo-code for example):

But this is still a very reliable, apparently deliberate trigger of a session kill by what is known to be a pretty stable and unflappable piece of software, so I am very puzzled what is going on. I also lack the expertise to file intelligent bug reports with the TT++ devs, so I am curious if anyone smarter than me sees something that might be falsely triggered in the code here.

Thanks I will keep debug for commands on while driving and see what turns up.