Closed marcgehman closed 4 months ago
Update: I was using the address directly to create a new queue, instead of dereferencing the queueAddress passed to the producer. Fixing that fixed the issue.
let warden = newWard[TestRef](queueAddress[], flags)
I would abstain from Wards if possible as they have had next to zero use and are heavily untested.
I made them for Disruptek on request and then he ignored their existence 🤣
Will be happy to help in any way should you have questions.
On Thu, 9 May 2024 at 11:22 AM, marcgehman @.***> wrote:
Update: I was using the address directly to create a new queue, instead of dereferencing the queueAddress passed to the producer. Fixing that fixed the issue.
— Reply to this email directly, view it on GitHub https://github.com/nim-works/loony/issues/35#issuecomment-2101862048, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN2EZW7EZXODKFVMIWK2LCDZBLTXPAVCNFSM6AAAAABHN5FWMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRHA3DEMBUHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Cool, will definitely take you up on that!
I 've been trying to use this library via the
Ward
objects, but I've been running into issues with segfaults.I tried setting up a consumer thread and a producer thread which each have a ward, and the consumer thread has the queue.
Running each thread individually works, but it seems there's some kind of race condition happening when they both interact which causes a segfault.