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

More rigorous testing of performance/memory safety #11

Open
brainkim opened this issue Jun 4, 2019 · 0 comments
Open

More rigorous testing of performance/memory safety #11

brainkim opened this issue Jun 4, 2019 · 0 comments

Comments

@brainkim
Copy link
Member

brainkim commented Jun 4, 2019

It would be embarrassing to argue that one of our key features of channels is memory safety and suffer from a memory leak bug. Figure out a way to rigorously test channels for memory growth.

Maybe something like the test from this issue: leebyron/iterall#25
@brainkim brainkim changed the title More rigorous testing of channel performance/memory safety. More rigorous testing of channel performance/memory safety Jun 6, 2019
@brainkim brainkim changed the title More rigorous testing of channel performance/memory safety More rigorous testing of performance/memory safety Sep 3, 2019
@brainkim brainkim mentioned this issue Sep 2, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brainkim