I had a loop in the declaration of a template which involved a while-loop that were to terminate once a variable increased beyond a certain value. In my haste I forgot to increment this value, and as a result, UPPAAL became unresponsive.
I suggest to implement some bound on the number of iterations that are tested, or an upper limit on the amount of time some code are allowed to run before UPPAAL stops checking it. This allows silly users (like me) to get in trouble. The problem is that there is no indications of the problem, and the user will need some knowledge of how UPPAAL works in order to find out that the code is the problem.
This is not a bug. It was a design decision to not unfold user declared functions. It is the users responsibility to ensure, that functions terminate. This should probably be documented better.
At best I will take this bug as a request for enhancement, but to be honest, I will get rather low priority.