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.

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

Avoid references to released bytes when taking a snapshot of an encoder #194

Merged
merged 1 commit into from
Dec 18, 2016

Conversation

robskillington
Copy link
Collaborator

cc @kobolog @xichen2020

This is to avoid the known case of Stream() taking a reference to a bytes slice that is returned to the pool from ostream.go when appending bytes with pool.AppendByte(..., bytesPool).

In the future we can build a dependency graph here using contexts to avoid copying, for now this will workaround the current free after use issues.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 77.226% when pulling 41c1ccd on copy-on-stream into 0ef731e on master.

@robskillington robskillington merged commit 03f7eb2 into master Dec 18, 2016
@robskillington robskillington deleted the copy-on-stream branch December 18, 2016 21:27
cw9 pushed a commit that referenced this pull request Oct 14, 2018
…e applicable (#194)

* Add MarkAllShardsAvailable to mark initializing shards available where applicable

* Use the algorithm API where possible
cw9 pushed a commit that referenced this pull request Oct 14, 2018
cw9 pushed a commit that referenced this pull request Oct 16, 2018
cw9 pushed a commit that referenced this pull request Oct 16, 2018
…e applicable (#194)

* Add MarkAllShardsAvailable to mark initializing shards available where applicable

* Use the algorithm API where possible
cw9 pushed a commit that referenced this pull request Oct 16, 2018
…e applicable (#194)

* Add MarkAllShardsAvailable to mark initializing shards available where applicable

* Use the algorithm API where possible
cw9 pushed a commit that referenced this pull request Oct 16, 2018
…e applicable (#194)

* Add MarkAllShardsAvailable to mark initializing shards available where applicable

* Use the algorithm API where possible
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants