Memory Profiling a Bud service
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
I'm wondering if there is a way to do a Memory Profiling in a Bud service because I'm noticing a possible memory leak.
I'm reading about the native Golang package [pprof](https://github.com/google/pprof/blob/main/doc/README.md), but to do this analysis is necessary to have access to the main package or routers.
The image below shows the service is using more and more memory, it doesn't stop.

I was using the **0.2.5** version and recently updated it to **0.2.8**, but it happens in both versions.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository files or tests; start by locating the Bud service's main package or routers and reviewing the linked Go pprof documentation. Done should mean a reproducible way to capture and analyze memory usage for a Bud service, with a clear determination of whether the reported growth is a leak.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100