In my opinion this problem could be related to the use of Weak Reference
to the subscriber instance, as the garbage collector could be disposing the subscriber instance in case there are no strong references to it. Therefore you should ensure that references to those instances are maintained alive to avoid disposing the
For example, as mentioned in the Prism documentation:
Module instances lifetime is short-lived by default. After the Initialize method is called during the loading process,the reference to the module instance is released. If you do not establish a strong reference chain to the module instance, it will be
garbage collected. And this behavior may be problematic to debug if you subscribe to events that hold a weak reference to your module, because your module just "disappears" when the garbage collector runs.
Based on this, please check that your subscription is still present by the time you publish the event.
Additionally, you could find more information about this and the use of
Weak References in the following MSDN article:
If you still can't solve this problem, it would be helpful if you could provide us with more information about your scenario or if you could isolate this behavior in a repro sample application and upload it to
SkyDrive or any other storage site you'd like to, and post the link here.