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.

Sign up for GitHub

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

Jump to bottom

Memory Profiler Build #54

Open
1 of 3 tasks
DennisSmolek opened this issue Apr 12, 2024 · 0 comments
Open
1 of 3 tasks

Memory Profiler Build #54

DennisSmolek opened this issue Apr 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@DennisSmolek
Copy link
Collaborator

DennisSmolek commented Apr 12, 2024 •
edited

With memory being the #1 killer for Jolt projects we should really ensure that at least the library devs are able and know how to setup debug environments and running the memory profiler at the same time.

Jrouwe's recent comment on a bug I had points to the ability to run the profiler while the app is running.

See the comment and what that looks like

  • Make sure the Memory Profiler build in the apps/examples folder is setup correctly
  • Add the CSS to display the profiler while the app is running
  • Test running the profiler with the app at the same time
@DennisSmolek DennisSmolek added the enhancement New feature or request label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DennisSmolek