I could to really figure out what is going on there, but this looks really, really wrong:
#14 0xae679dca in SwRootFrm::~SwRootFrm (this=0x8b42e40, __in_chrg=<value
optimized out>)
at
/data/opt/libreoffice/libreoffice-3-4/sw/source/core/layout/newfrm.cxx:606
#15 0xae679e3b in SwRootFrm::~SwRootFrm (this=0x8b42e40, __in_chrg=<value
optimized out>)
at
/data/opt/libreoffice/libreoffice-3-4/sw/source/core/layout/newfrm.cxx:624
To me that looks like the SwRootFrm thinks it is a member of itself. It calls its own destructor on the same instance (itself) upon leaving the scope of the destructor. While I think that cant be right, it can be even less right with the SwRootFrm being owned by the ViewShell (via boost::shared_ptr<>), so the only one ever calling a ~SwRootFrm destructor should be that shared_ptr<>.
Unfortunately, I havent figured it out completely -- all I see is that I jump from the last line of the destructor to the first one of it in the debugger.
Most likely the cause is somewhere in writer:0382ef89c6631ec39b98b63dbdadd85ecea11275, but that one is not-so-small.
I could to really figure out what is going on there, but this looks really, really wrong: :~SwRootFrm (this=0x8b42e40, __in_chrg=<value libreoffice/ libreoffice- 3-4/sw/ source/ core/layout/ newfrm. cxx:606 :~SwRootFrm (this=0x8b42e40, __in_chrg=<value libreoffice/ libreoffice- 3-4/sw/ source/ core/layout/ newfrm. cxx:624
#14 0xae679dca in SwRootFrm:
optimized out>)
at
/data/opt/
#15 0xae679e3b in SwRootFrm:
optimized out>)
at
/data/opt/
To me that looks like the SwRootFrm thinks it is a member of itself. It calls its own destructor on the same instance (itself) upon leaving the scope of the destructor. While I think that cant be right, it can be even less right with the SwRootFrm being owned by the ViewShell (via boost:: shared_ ptr<>), so the only one ever calling a ~SwRootFrm destructor should be that shared_ptr<>.
Unfortunately, I havent figured it out completely -- all I see is that I jump from the last line of the destructor to the first one of it in the debugger.
Most likely the cause is somewhere in writer: 0382ef89c6631ec 39b98b63dbdadd8 5ecea11275, but that one is not-so-small.