On 09/05/2011 09:41, Andor E wrote: > Could you think of a quick and dirty hack to work around this? I'm > building my own OOo, so I wouldn't mind using a hack as long as it > works :). Sadly I'm stuck with OOo 3.2.1 for quite some time.
there is a dirty hack for one of the problems. put a SolarMutex guard into SwClient::~SwClient. (just grep SolarMutex in sw, it's always the same one line) this is architecturally completely wrong, and could theoretically lead to deadlocks (but probably won't in practice), but perhaps it makes it "stable enough" for you. for the other problem (the dead UNO objects handed out by factory functions) i cannot think of a workaround. back when i worked on this, after i put in the SolarMutex guard in the various UNO object destructors to solve the first problem, it then started crashing because of the second problem; if you're unlucky you'll have the same experience... -- "It is a profoundly erroneous truism, repeated by all copy-books and by eminent people when they are making speeches, that we should cultivate the habit of thinking of what we are doing. The precise opposite is the case. Civilisation advances by extending the number of important operations which we can perform without thinking about them. Operations of thought are like cavalry charges in a battle -- they are strictly limited in number, they require fresh horses, and must only be made at decisive moments." -- Alfred North Whitehead -- ----------------------------------------------------------------- To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
