PRB: Shared Property Manager Does Not Manage Interface Pointers (242554)

MORE INFORMATION

The Shared Property Manager (SPM) gives components a way to store and share "stateful" information. For objects to share state, they must be running in the same server process.

SPM is useful for storing simple variables (strings, integers, arrays). You should not put references and interface pointers into the SPM because it does not do any marshalling and unmarshalling of interface pointers. It is just memory with some lock mechanisms in place. Therefore, problem will occur when you store interface pointers for apartment threaded components and then try to use them on the wrong thread.

Because apartment model components can only run on the thread that they were created on, the potential of two components waiting on the same thread also could occur and lead to a deadlock.

If you put object references in SPM, it simply AddRefs your object reference in the storing apartment and hands out cross-apartment references to objects in other activities or apartments. This will lead to erroneous results. Instead, any object references your object holds as data members have to be stored as apartment-neutral GIT cookies.

The GIT will do marshalling when storing object references and hand you back a cookie. This cookie can then be stored in the SPM.