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

registerFilter and processAllClasses get called again. #993

Open
Froze-N-Milk opened this issue Jul 17, 2024 · 0 comments
Open

registerFilter and processAllClasses get called again. #993

Froze-N-Milk opened this issue Jul 17, 2024 · 0 comments

Comments

@Froze-N-Milk
Copy link

While this issue has not happened to me, I've seen several teams have it, and
there doesn't seem to be a particularly apparent cause / solution.

The following errors are produced on the DriverStation:

Class processing had already started when registerFilter() was called. You must 
register your class filter before processAllClasses() is called in 
FtcRobotControllerActivity.

processAllClasses() should only be called by the system. Any additional calls 
are ignored.

These can only occur when the AtomicBoolean processAllClassesCalled on
org.firstinspires.ftc.robotcore.internal.opmode.ClassManager has been
set to true.

I would imagine that this is occurred by a soft restart of the application caused
by a previously caught crash.

These issues are not caused by users manually calling this process again.

There seems to be a general consensus that this issue is caused by something to
do with vision pipelines.

One team has reported that the issue was caused by low battery and a crash
related to being unable to find their webcam.

It would be helpful for teams that have experienced this issue to add their
experiences resolving it, and logcat files to this issue.

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

1 participant