[Bug]: Polyscope reported as using significant energy while not doing work

Open
#136 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
desktop, performance

Research direction

Reproduce on macOS Tahoe running ARM64 with PolyScope 0.16.0, then observe its Energy Impact while the app is idle. Done means the idle application no longer reports significant energy use; the payload names no files, tests, or entry points to inspect.

Written by the indexing model from the issue text.

Description

Platform

macOS

Operating system version

macOS Tahoe

System architecture

ARM64 (M1, M2, etc)

PolyScope Version

0.16.0

Bug description

I noticed my battery draining fast lately, and I found that Polyscope is being reported as an offender. This was while Polyscope wasn't doing work.

Image
Steps to reproduce

No response

Relevant log output
Dominant language
No language data
Stars
20
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beyondcode/polyscope-community

All issues in beyondcode/polyscope-community

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.