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

BufferRecycler access not safe if readers/writers used from different threads #69

Closed
cowtowncoder opened this issue Sep 12, 2019 · 0 comments

Comments

@cowtowncoder
Copy link
Member

(note: related to FasterXML/woodstox#82)

The way buffer recycling works with BufferRecycler assumes that not only is access to reading, writing single-threaded (which typically is true), access to any particular parser, generator is from a single thread. But this is not necessarily true, especially in case of async parsing where processing thread may change over time in pipeline setups for example.

Handling should be changed to make this usage safe, using experience from Jackson and Woodstox on adding simple safeguards and synchronization.

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

No branches or pull requests

1 participant