Skip to content

Conversation

@santigimeno
Copy link
Member

@santigimeno santigimeno commented Jul 24, 2025

On runtime shutdown, when continuous profiling is enabled, it can happen that we try access GrpcAgent::cont_prof_queue_ when it has already being reset, thus crashing the process.

Summary by CodeRabbit

  • Bug Fixes
    • Improved stability by adding an additional safety check to prevent operations on uninitialized or destroyed resources during profiling.

@santigimeno santigimeno self-assigned this Jul 24, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jul 24, 2025

Walkthrough

A static callback function in the gRPC agent implementation was updated to include an additional null check. Now, the function returns early if either the agent pointer or its internal profile queue is null, enhancing safety before attempting to enqueue profile data.

Changes

Cohort / File(s) Change Summary
gRPC Agent Implementation
agents/grpc/src/grpc_agent.cc
Added a null check for the internal profile queue in a static callback function, ensuring early return if the queue is uninitialized or null.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a check, a pointer or two,
The agent now guards what the queue tries to do.
With safety in mind and a hop in its step,
The callback avoids any null-pointer rep.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4163c74 and 4a13325.

📒 Files selected for processing (1)
  • agents/grpc/src/grpc_agent.cc (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • agents/grpc/src/grpc_agent.cc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: build-docs
  • GitHub Check: test-linux (ubuntu-24.04-arm)
  • GitHub Check: lint-js-and-md
  • GitHub Check: coverage-windows
  • GitHub Check: test-linux (ubuntu-24.04)
  • GitHub Check: build-tarball
  • GitHub Check: test-macOS
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch santi/fix_cont_prof_crash

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

On runtime shutdown, when continuous profiling is enabled, it can happen
that we try access `GrpcAgent::cont_prof_queue_` when it has already
being reset, thus crashing the process.
@santigimeno santigimeno force-pushed the santi/fix_cont_prof_crash branch from 4163c74 to 4a13325 Compare August 5, 2025 20:14
santigimeno added a commit that referenced this pull request Aug 6, 2025
On runtime shutdown, when continuous profiling is enabled, it can happen
that we try access `GrpcAgent::cont_prof_queue_` when it has already
being reset, thus crashing the process.

PR-URL: #348
Reviewed-By: Rafael Gonzaga <[email protected]>
@santigimeno
Copy link
Member Author

Landed in 7cd0229

@santigimeno santigimeno closed this Aug 6, 2025
@santigimeno santigimeno deleted the santi/fix_cont_prof_crash branch August 6, 2025 09:28
santigimeno added a commit that referenced this pull request Aug 25, 2025
On runtime shutdown, when continuous profiling is enabled, it can happen
that we try access `GrpcAgent::cont_prof_queue_` when it has already
being reset, thus crashing the process.

PR-URL: #348
Reviewed-By: Rafael Gonzaga <[email protected]>
santigimeno added a commit that referenced this pull request Aug 26, 2025
On runtime shutdown, when continuous profiling is enabled, it can happen
that we try access `GrpcAgent::cont_prof_queue_` when it has already
being reset, thus crashing the process.

PR-URL: #348
Reviewed-By: Rafael Gonzaga <[email protected]>
PR-URL: #359
Reviewed-By: Juan José Arboleda <[email protected]>
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.

3 participants