-
Notifications
You must be signed in to change notification settings - Fork 751
Closed
Description
Hi, I'm maintain a golang binding for hyperscan, there is a strange crash issue was reported, which can be reproduced after thousands of scan vector calls.
This stack trace comes from running this test program.
It seems some memory was corrupt, are there any pointer will be saved in the compile and scan phases? Because golang use a GC to manage all the memory, the GO pointer passed to hyperscan can't be saved after call.
Besides, I also tried to lock the scanning goroutine to its current thread with runtime. LockOSThread
, but it seems no effects.
Thanks
Metadata
Metadata
Assignees
Labels
No labels