Preemptive Thread String Crash

[Mike_D]

@Kem_Tekinay

My understanding is that properties are protected internally. It’s still a good idea, but shouldn’t be necessary to prevent a crash.

We need Xojo to clarify this, but here’s what they wrote:

[1]

Xojo has done a good job of making a lot of the framework safe, but that just means your app shouldn’t crash if, say, the Thread tries to manipulate a variable at the same time as other code. It’s up to you to make sure one area of your app doesn’t clobber the changes made by another.

and

[2]

What things are thread-safe?

We’ve updated our framework to safeguard areas that were previously not preemptive thread-safe. For the most part, our entire framework is now safe for concurrent use with preemptive threads, with a few exceptions like XojoScript and Runtime.IterateObjects. When sharing resources such as MemoryBlocks, Dictionaries, or Arrays among threads, you may need to use CriticalSections or Semaphores to ensure safe access. However, if you’re only reading from these resources without modifying them, synchronization is not required. You’ll be happy to know that calling Thread.AddUserInterfaceUpdate from a preemptive thread is also safe.

Links:
[1] Preemptive Threads Are Here, and They Are… Pretty Good
[2] Cooperative to Preemptive: Weaving New Threads into your Apps