You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, there are several data races in the SDK as of version 6.5.11.
As an example, IterableEmbeddedManager stores some memory for placements and their associated messages. This memory is not protected and is accessed from multiple threads. This can lead to memory corruption and instability. Access to this memory should be synchronized if it accross threads.
class IterableEmbeddedManager:NSObject,IterableInternalEmbeddedManagerProtocol{...privatevarmessages:[Int:[IterableEmbeddedMessage]]=[:]...publicfunc getMessages()->[IterableEmbeddedMessage]{ << not isolatedreturnArray(messages.values.flatMap{ $0 })}...privatefunc retrieveEmbeddedMessages(completion:@escaping()->Void){
apiClient.getEmbeddedMessages().onCompletion(
receiveValue:{ embeddedMessagesPayload in
..
let processor =EmbeddedMessagingProcessor(currentMessages:self.messages,<<<< URLSession-Delegate Queue
fetchedMessages: fetchedMessagesDict)...
private func setMessages(_ processor:EmbeddedMessagingProcessor){ << not isolated, called from several different threads
messages = processor.processedMessagesList()cleanUpTrackedMessageIds(messages)}...
public func reset(){letprocessor=EmbeddedMessagingProcessor(currentMessages:self.messages, fetchedMessages:[:])self.setMessages(processor) << Message access on main thread
The text was updated successfully, but these errors were encountered:
Hey @macbellingrath thanks for surfacing this, our team will take this note into our next internal discussion on upcoming improvements. Let me know in our Support thread if anything misbehaves.
Hello, there are several data races in the SDK as of version 6.5.11.
As an example, IterableEmbeddedManager stores some memory for placements and their associated messages. This memory is not protected and is accessed from multiple threads. This can lead to memory corruption and instability. Access to this memory should be synchronized if it accross threads.
The text was updated successfully, but these errors were encountered: