setRadioChannel(0) causes C Stack overflow

[xerox8521]

So im experienting with MTA and Lua and noticed that setRadioChannel(0) didnt work for me at first so i added it in the onClientPlayerRadioSwitch event which works but causes a C Stack Overflow.

addEventHandler("onClientPlayerRadioSwitch",getRootElement(),function()  
  
    local vehicle = getPedOccupiedVehicle(localPlayer) 
    if(vehicle) then 
        if(getElementModel(vehicle) == 432) then 
            setRadioChannel(0) 
            cancelEvent() 
        end 
    end 
     
end) 

Edit it seems it doesnt matter which radio number you enter and it doesnt matter if you cancel the event or not

[rtx]

setRadioChannel may be triggering 'onClientPlayerRadioSwitch'!

Actually from the looks of it, I would say it definitely triggers that event.

[0xCiBeR]

In effect, it does trigger that event, so it's cycling the same function over and over causing a stack overflow.

[TAPL]

addEventHandler("onClientPlayerRadioSwitch", root, 
function() 
    local vehicle = getPedOccupiedVehicle(localPlayer) 
    if (vehicle) then 
        if (getElementModel(vehicle) == 432) then 
            if getRadioChannel() ~= 0 then 
                setRadioChannel(0) 
                cancelEvent() 
            end 
        end 
    end 
end) 

[darhal]

Well stack overflow is a function that call another function which call the first function this called a trail function You should visit lua user wiki to see how to fix it !

[0xCiBeR]

addEventHandler("onClientPlayerRadioSwitch", root, 
function() 
    local vehicle = getPedOccupiedVehicle(localPlayer) 
    if (vehicle) then 
        if (getElementModel(vehicle) == 432) then 
            if getRadioChannel() ~= 0 then 
                setRadioChannel(0) 
                cancelEvent() 
            end 
        end 
    end 
end) 

Should fix it perfectly.

[ixjf]

Well stack overflow is a function that call another function which call the first function this called a trail function You should visit lua user wiki to see how to fix it !

Not necessarily caused by infinite recursion, but in this case that's more or less it indeed.