You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
(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.
The text was updated successfully, but these errors were encountered: