Open Shading Language discussion list Upcoming Events OSL TSC meeting ( every other week ) When: Thursday, October 14, 2021, 2:00pm to 3:00pm (GMT-07:00) America/Los

OSL TSC meeting ( every other week ) When: 09/30/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/30/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/30/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/30/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Wondering if anybody would object to the following changes to minimum dependencies -- only for master branch going forward and the NEXT major release of OSL (obviously not dropping support from

Open Shading Language discussion list Upcoming Events OSL TSC meeting ( every other week ) When: Thursday, September 30, 2021, 2:00pm to 3:00pm (GMT-07:00) America/Los

Reminder: OSL TSC meeting ( every other week ) When: 09/30/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Yup. Took some rearchitecting, but it works with 12 threads. Thanks, Mark

Are you saying you've fully figured it out? -- Larry Gritz lg@...

And that smell would be weird. I have two/N distinct contexts, but the way I was using them I would use an SC from one thread in a different one leading to the corruption. Thanks, Mark

It sure smells like you have two threads simultaneously messing with the same closure pool, which should never happen. Are you EXTRA SURE that the threads are each using their own distinct

* frame #0: 0x00007fff7270733a libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x00007fff727c3e60 libsystem_pthread.dylib`pthread_kill + 430 frame #2: 0x00007fff7268e808

With a debug build, can you get a stack trace at the point that the assertion is hit? That looks like an assertion in SimplePool::alloc(). But I'm not sure what could go wrong. Maybe something that

Hoping for some insight. I’ve bootstrapped OSL into a custom renderer and for the most part my simple scene is working on a single thread( the shader is three layers, marble->checkerboard (Cb)->

Open Shading Language discussion list Upcoming Events OSL TSC meeting ( every other week ) When: Thursday, September 30, 2021, 2:00pm to 3:00pm (GMT-07:00) America/Los

OSL TSC meeting ( every other week ) When: 09/16/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/16/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/16/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Thanks Larry!