Delegate "access violation reading location"
Hello Epic and Friends!
I have a delegate and a queue that is being populated in another thread and I am running into what I would consider some confusing behavior. The delegate is bound on construction of an object on the main thread, and is executed on the main thread only.
I believe I am doing things in a thread safe manner here but as the deep intricacies of c++ and indeed threading in general are still mysterious to me, I was wondering if any part of this stands out as bad practice, or if there is an explainable reason as to why this is happening.
Follow this question
Once you sign in you will be able to subscribe for any updates here