Qtox: Being spam called causes qTox to use extremely high CPU until restarted

[avirunes]

Brief description: Being spam called on qTox causes it to use 60%+ cpu until it is restarted

Operating System: Windows 10
qTox version: v1.12.1
toxcore version: 0.1.10

Reproducible: Always

Steps to reproduce:

1. Have a person on the other end call and hang up very quickly

Observed Behavior:
CPU usage spikes from 1% up to over 60% and stays there until the program is restarted

Expected Behavior:
CPU usage to spike slightly when being called and to revert to normal when the call is declined / canceled

Additional info:
++++++++
https://i.imgur.com/5MAdAuE.png
++++++++
CPU usage while being called, the program needs to be restarted for this to go back to normal

[usparvxj]

He tested this with me as well - He called me and hung up immediately 10x as fast as possible, and my qtox process took 70-90% CPU until it had to be killed with kill -9 pid, I couldn't kill the process normally

My version is newest (~2 days) nightly compiled for debian, so this is cross platform issue

Edit: Just tried having him do it again after restarting so I could get a screenshot too, but it didn't do it that time, he did it ~40 times and my CPU spiked to ~10% but didn't max it out like before, so it doesn't seem to do it every time

[sudden6]

Can you please upload the logs when the problem occurs?

[usparvxj]

Here's a screenshot after I made a 2nd profile to test with myself (I spam called newtest and the terminal output is showing what happened)

For the qtox.log file - there is only one file there and it's called qtox.log, so I'm assuming all qtox clients running log to the same file? I hope that doesn't cause a problem but here are relevant lines (both logs I pasted show from after logging in successfully until after force closing the offending client)

[17:20:59.832 UTC] :0 : Warning: QObject::startTimer: Timers cannot be started from another thread
[17:21:00.531 UTC] :0 : Warning: QObject::startTimer: Timers cannot be started from another thread
[17:21:35.007 UTC] core/coreav.cpp:717 : Warning: "Rejecting call invite from 0, we're already in that call!"
[17:21:36.557 UTC] core/coreav.cpp:766 : Warning: Call with friend 2 died of unnatural causes!
[17:21:36.707 UTC] core/coreav.cpp:766 : Warning: Call with friend 2 died of unnatural causes!
[17:21:37.456 UTC] core/coreav.cpp:766 : Warning: Call with friend 2 died of unnatural causes!
[17:21:38.307 UTC] :0 : Warning: QObject::startTimer: Timers cannot be started from another thread
[17:21:40.957 UTC] :0 : Warning: QObject::startTimer: Timers cannot be started from another thread

And from a second test

[17:34:08.447 UTC] core/coreav.cpp:717 : Warning: "Rejecting call invite from 0, we're already in that call!"
[17:34:11.907 UTC] :0 : Warning: QObject::startTimer: Timers cannot be started from another thread
[17:34:14.557 UTC] :0 : Warning: QObject::startTimer: Timers cannot be started from another thread

Happened the first 2 times I tried; after both times I had to kill with kill -9 to close that client

[Conor-OLD]

I can confirm the same issue, on Windows 7 Professional SP1.

[ernbcaan]

anyone have fix for this ? having same problem on ubuntu 16.0.4 and I need to restart computer sometimes when I get called

have to use skype for audio call as result of this right now

[sudden6]

Did any of you try the newest qTox v1.13.0?

[usparvxj]

@sudden6

Did any of you try the newest qTox v1.13.0?

I just recompiled qTox using the newest nightly again (and used the old release of toxcore due to this issue) and still have the problem when calling myself on a different profile

I also tested calling my friend on Windows (1.13.0 x64 bit) a bunch and it happened to him again

Edit: Screenshot of rogue threads which never end