Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After approx 30sec CFA app stops working #78

Open
chewbacca70 opened this issue Feb 1, 2022 · 3 comments
Open

After approx 30sec CFA app stops working #78

chewbacca70 opened this issue Feb 1, 2022 · 3 comments

Comments

@chewbacca70
Copy link

chewbacca70 commented Feb 1, 2022

After approx 30sec CFA app stops working. I am using iPhone13 ios13.5.1
Any Idea why this happens, unfortunately I cant provide any logs as the provider still runns like expected.

BR

@chewbacca70 chewbacca70 changed the title After 1-2 minutes device screen dissapears After approx 30sec CFA app stops working Feb 21, 2022
@chewbacca70
Copy link
Author

chewbacca70 commented Mar 7, 2022

It seems there is too much CPU usage when running CFAgent-Runner, anybody has the same issue, and Idea why this happens?

symptomsd(SymptomEvaluator)[129] : Fatal RESOURCE_NOTIFY trigger for CFAgent-Runner [486] (48000541916 nanoseconds of CPU usage over 53.00s seconds, violating limit of 48000000000 nanoseconds of CPU usage over 60.00s seconds)

@sai-tirunagiri
Copy link

Even I am facing the same issue, also I see there is no point posting issues in hea as @nanoscopic no longer supports this project on open source!

I suspect this to be some library issue which is spiking the cpu utilisation, I will let you know if I find something.

@vaclcer
Copy link

vaclcer commented Apr 2, 2022

Exactly the same issue. The connection freezes after approx. 40+ seconds every time on iPhone 8. No logs on providers side, even with -debug switch on. The problem is indeed:

"cpu ... exceeding limit of 80% cpu over 60 seconds".

Any news on this one? Thanks!

crash-dump.log

EDIT:

OK, I think have found a workaround. Switching to:

videoMode: "app"

in devices settings in config.json solves this by using a more efficient way of sending video output (I guess). Hence lower CPU usage, hence more stable CFA.

@nanoscopic you do not make this very easy for us - I have spent a lovely weekend playing with the code, reading through github issues, commits and your comments in the code :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants