"I can post a video of the crashes if it would help" Yes please. We'll take whatever we can get. We definitely want to find and fix these gremlins.
I just tried the example of deleting a processor with a non empty queue to get the error popup. The results worked as expected. Thanks Joe On Sat, Jun 25, 2016 at 4:14 PM, ddewaele <ddewa...@gmail.com> wrote: > I got rid of the large merges yesterday and switched to a two phase merge. > That indeed solved a lot of issues. > > But I think I can reproduce the UI hang ..... > > It seems to always occur after performing an action in the flow where a > previous action resulted in an error / warning message : > > Example : > > - Attempting to delete a processor that is in the process of shutting down > shows an error (popup) > - Deleting a processor that has a non-empty queue attached to it results in > an error (popup) > > If you execute a simple refresh on the UI after these messages it will hang. > (I can post a video of the crashes if it would help) > > > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/UI-can-take-a-very-long-time-to-become-available-tp12201p12267.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
