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

calling the continuation method even on frame alloc failure #12167

Conversation

remibettan
Copy link
Contributor

Tracked by: RSDEV-537

@remibettan remibettan requested a review from Nir-Az September 6, 2023 10:21
if (!fh.frame)
{
LOG_INFO("Dropped frame. alloc_frame(...) returned nullptr");
return;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe better to move the memcpy log to after this block (without moving the time setting itself)?

if( diff > 10 )
                        LOG_DEBUG( "!! Frame memcpy took " << diff << " msec" );

Otherwise we might see a weird like

!! Frame memcpy took " << diff << " msec
Dropped frame. alloc_frame(...) returned nullptr

@Nir-Az Nir-Az merged commit d967045 into IntelRealSense:development Sep 7, 2023
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

Successfully merging this pull request may close these issues.

2 participants