-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
T265: Attempt to save a map very often ends in "null pointer passed for argument "buffer"" #5683
Comments
|
Thanks Jim. This is what I wanted to comment. I have this pretty often, too often, to be honest, to be not concerned while pressing the "Save" button. Most of the times this is accompanied by a second attempt, which seem to work, but then either stop or a new start does not work and the stack claims "no device connected". The common solution is to power-cycle the cam (not a solution of course :)) |
We have been able to reproduce this. Thanks for the report, @neilyoung. |
Oh great. Thanks for confirmation. |
closed for lack of interest |
But still present |
Issue Description
As subject says: What could be the reason for this problem? Comes out of the sudden. I can already have saved the map a couple of times successfully. It can be, that this situation is solved by re-starting. The map is not even corrupted and accepted on load. But there were also cases, in which I had to replug the cam in order to recover from that, IMHO an absolute NOGO for productive scenarios.
The text was updated successfully, but these errors were encountered: