Skip to content

Conversation

@paperbenni
Copy link
Member

@paperbenni paperbenni commented Feb 1, 2026

⚡ Bolt: Optimize drawstatusbar memory allocation

💡 What:
Replaced heap allocation (malloc/free) with stack allocation (char buf[1024]) in drawstatusbar for strings that fit within the standard 1024-byte limit. Added a fallback to malloc for larger strings to ensure safety.

🎯 Why:
drawstatusbar is called frequently (e.g., every second or more on status updates). Avoiding malloc reduces allocator overhead and fragmentation in this hot path.

📊 Impact:
Removes one malloc/free pair per status bar redraw for normal usage.

🔬 Measurement:
Verified by inspection and successful build (make clean && make). The code logic ensures malloc is only used when necessary and memory is correctly freed.


PR created automatically by Jules for task 3776993879807769484 started by @paperbenni

Summary by Sourcery

Enhancements:

  • Prefer stack allocation for drawstatusbar buffers and free heap memory only when the fallback path is used.

Reduces memory allocation overhead in the frequent status bar update path by using a stack buffer for strings up to 1024 bytes. Fallbacks to malloc for larger strings.

Co-authored-by: paperbenni <15818888+paperbenni@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai
Copy link

coderabbitai bot commented Feb 1, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bolt-optimize-drawstatusbar-3776993879807769484

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sourcery-ai
Copy link

sourcery-ai bot commented Feb 1, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

drawstatusbar now prefers an on-stack 1 KiB buffer and only falls back to heap allocation for longer status strings, eliminating malloc/free in the hot path under normal workloads; the new log entry documents this micro-optimization.

Flow diagram for drawstatusbar buffer selection

flowchart TD
    A["Start drawstatusbar"] --> B["Compute len = strlen(stext) + 1"]
    B --> C{"len > sizeof(buf)?"}
    C -- Yes --> D["Allocate heap buffer malloc(len)"]
    D --> E["Copy stext into heap buffer"]
    E --> G["Render status text"]
    C -- No --> F["Use stack buffer buf"]
    F --> E
    G --> H{"Heap buffer used?"}
    H -- Yes --> I["free heap buffer"]
    H -- No --> J["Skip free"]
    I --> K["Return"]
    J --> K
Loading

File-Level Changes

Change Details Files
drawstatusbar uses stack storage for typical status strings and conditionally allocates heap memory only when needed, freeing it after use.
  • allocate a 1024-byte local buffer and initialize the heap pointer to NULL
  • copy incoming text into the stack buffer when it fits, otherwise malloc space and remember the pointer for eventual free
  • guard the free call so only heap-allocated buffers are released
bar.c
Add a Bolt metadata note describing the optimization rationale.
  • create .jules/bolt.md summarizing the hot-path allocation change and motivation
.jules/bolt.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • Consider tying the 1024-byte stack buffer size to the existing global status text limit (e.g., via a shared constant or macro) so they can't silently diverge in the future.
  • You can simplify the allocation logic slightly by only tracking a separate heap_buf pointer for the malloc case instead of overloading p, keeping text as the sole working buffer.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider tying the 1024-byte stack buffer size to the existing global status text limit (e.g., via a shared constant or macro) so they can't silently diverge in the future.
- You can simplify the allocation logic slightly by only tracking a separate `heap_buf` pointer for the malloc case instead of overloading `p`, keeping `text` as the sole working buffer.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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.

1 participant