I ran into something very similar with Action! recently, especially after one of the updates. In my case, it turned out to be a conflict with the rendering mode.