No there is no specific reason.
The target_link_libraries was legacy code and we weren't aware that it could done like you proposed.

This is our module cmake file.

Ok I understand that, but my problem is something else.

That is interesting to know, that was absolutely not intended and surely was the root of our problems.
From which part of the stack trace were you able to extract this information?

Here is the output:

Did some debugging and what I found out so far was:

I can do that, but could you tell me how to save the output, so it's of any use for you?

I guess it had something to do with our selfcompiled VTK and GDCM.
Right now it is working fine at our site.

We are using mitk 2015.05.2

We are experiencing exactly this issue.

VTK Polydata

I have very similar problems, the program crashes quite often doing a global reinit after adding a new node.

We had the same problem with MITK 2014.10 and the attached patch solved the problem for us as well.