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

[BUG] On iOS, RTAB-Map crashes after pressing "stop" button in data recording mode #1420

Open
ser94mor opened this issue Dec 23, 2024 · 2 comments

Comments

@ser94mor
Copy link

ser94mor commented Dec 23, 2024

From my experience, in 95% of cases of data collection sessions in data recording mode, I observe RTAB-Map app crashes after pressing the "stop" button.

The iPhone is configured to record data at maximum frequency.

This behaviour is observed on both iPhone 15 Pro and iPhone 12 mini.

[ANOTHER BUG]
If the iPhone battery level is slightly higher than 20%, one starts a data collection session in data recording mode, and then the battery level drops below 20%, iPhone displays a pop up window suggesting to put iPhone into the Power Saving mode, which, in turn, triggers RTAB-Map app crash. Would be good if the RTAB-Map app didn't stop data recording when pop up windows appear.

Both issues are observed on the RTAB-Map iOS 0.21.8 app installed from AppStore.

@matlabbe
Copy link
Member

matlabbe commented Dec 26, 2024

That recording feature is somewhat experimental, I am not surprised of these issues. At max frequency (60 Hz), I didn’t test it more than 1 min or 2. At 1 Hz (default), it should last minutes to hours in theory, but I didn’t test for hours.

How long are your recordings?

For the 20% battery warning, iOS may be pushing back the app in background, turning off ARKit. I think continuing recording afterwards, assuming we have to reinitialize ARKit , would not make sense because the poses would not be continuous. The app would need however to close the current session and save it, asking the user to start another session.

@ser94mor
Copy link
Author

@matlabbe , thank you for the response.

My recordings usually last from 3 to 15 mins.

About the 20% problem:
Maybe it still makes sense to continue recording after ArKit reinitialization because you then can manually identify the moment of failure and split the recording into two removing the nodes(records) that were captured during the reinitialization period.

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

No branches or pull requests

2 participants