Open sentry-io[bot] opened 2 months ago
Yikes, no results on Google:
While debugging a separate issue related to hyperscan, I stumbled upon a docstring that explains this error:
/**
* The scratch region was already in use.
*
* This error is returned when Hyperscan is able to detect that the scratch
* region given is already in use by another Hyperscan API call.
*
* A separate scratch region, allocated with @ref hs_alloc_scratch() or @ref
* hs_clone_scratch(), is required for every concurrent caller of the Hyperscan
* API.
*
* For example, this error might be returned when @ref hs_scan() has been
* called inside a callback delivered by a currently-executing @ref hs_scan()
* call using the same scratch region.
*
* Note: Not all concurrent uses of scratch regions may be detected. This error
* is intended as a best-effort debugging tool, not a guarantee.
*/
#define HS_SCRATCH_IN_USE (-10)
Here's the description of a scratch-space from the dev-reference page:
Huh, weird. I guess this means we can do a retry as our best hope? I'm not sure how we're accessing the scratch region from multiple threads?
This one has occurred once so far:
Sentry Issue: COURTLISTENER-75S
Filed by: @albertisfu