-
-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Macos processes #118
Macos processes #118
Conversation
…proxy_rs into macos-processes
not too much unsafe blocks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work! 🚀
Fantastic to see that enumeration now works without instantiating all those NSRunningApplications, great job. 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good now! Few smaller comments inline below.
The final thing I'm worried about here is memory leaks in the unsafe code. I suppose this is not super easy to test though. At the very least, can we maybe have some (#[ignore]
d by default) test cases that call the unsafe methods (e.g. tif_data_for_executable
) in a loop so that one can manually check for an increase in memory? Does that make sense? Smarter ideas are welcome as well of course, but I don't want to overcomplicate things.
This is a first draft to get first info from running processes:
there are a lot of steps before the png image (NSImage -> tif_representation -> bitmap_representation -> png_representation), maybe we can optimize that part