Hi, WIX Devs
Thanks for such a great tool!
I have a problem developing my own installers with Wix.
I defined several custom actions in a DLL, these functions share a same
behavior that they need to send the instrumentation data to our server
through HTTP request.
When WIX calls a custom action, as my observation, it starts a new thread
for the function, and the thread exits after the function is returned.
However, the problem is when the thread exits, *the heap storage created in
the custom action thread is also removed*! Which leads to a crash when HTTP
callback thread tries to access the objects created in the heap.
What described above is only my observation, I just want to confirm whether
this is really the memory management method of thread adopted by WIX
(something like ThreadLocal, if I understand correctly), therefore we can
think about other ways for solution.
Thanks,
Yun
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
