I found that the image_view nodelet (image_view/image) does not update its window and hangs in some cases. I think this is because the nodelet manager can execute a callback in multiple threads even if the callback is associated to a threaded callback queue (see https://github.com/ros/nodelet_core/blob/2f25b775fd0241fc949a5fc002e718dbd142d5d7/nodelet/src/callback_queue_manager.cpp#L206), although the callback must be called by a specific thread to successfully update the window.

The following is a launch script to reproduce the problem. I am afraid that the problem may not be reproduced in different environment because the problem depends on environment-specific threading but I hope this is helpful.

<launch>
    <node name="image_view_node" pkg="nodelet" type="nodelet" 
          args="manager image_view_node" output="screen"/>

    <node name="image_view_loader" pkg="nodelet" type="nodelet" 
          args="load image_view/image image_view_node" output="screen"/>

    <node name="image_view_loader2" pkg="nodelet" type="nodelet" 
          args="load image_view/image image_view_node" output="screen"/>

    <!-- An external node publishing sensor_msgs/Image on the "image" topic is required -->
</launch>

I think the only solution is to add a new thread updating the window and am writing a workaround. Please see if interested.
https://github.com/yoshito-okada/image_pipeline/tree/fix_image_view_nodelet