|
Thanks for the quick response :-)
Can you elaborate? Could these changes affect the way my Lua & OS threads work together? (i.e. is there anything I need to be aware of, or change, when migrating up to 5.2)(This makes tight loops that do not create objects "atomic", however.)
Thanks! Matt On 22/07/28164 20:59, Roberto Ierusalimschy wrote:
Could you please confirm that the Lua 5.2.0 work 3 includes the fix to this GC-in-another-thread-while-jump issue?I moved the threadyield call to points where the GC may be called; these points can trigger finalizers and therefore Lua must be ready to all kinds of changes there. (This makes tight loops that do not create objects "atomic", however.) -- Roberto