jar398
commented
9 years ago I was the one to report this. It was not discovered under load testing but just under ordinary use. And there was no crash, but rather it just hung (spinning rainbow) for longer than I was willing to wait. Since the browser was useless I killed it.
If I had waited longer perhaps I would have seen the tree. On the other hand a frozen browser is a pretty severe failure mode. I think we'd want either confirmation ("that tree is really big, are you sure you want to open it?" - like emacs does) or a progress meter.
I would even say it's a bug in Firefox that javascript in one tab can monopolize the whole browser.
Low priority I guess.
On Tue, Feb 17, 2015 at 3:26 PM, Jim Allman notifications@github.com wrote:
Need to reproduce this. It was discovered by a user (who?) in load testing.
"earlier today I tried to view a 60,000 node tree… got the spinning rainbow for many minutes, and finally just blew away the whole browser"
Which study + tree?
"pg_438 I think, first tree... if it's not 438 it's one of these: pg_2597, pg_391, pg_1160, pg_438, pg_1744, pg_1065, pg_738, pg_2264, pg_2283"
— Reply to this email directly or view it on GitHub https://github.com/OpenTreeOfLife/opentree/issues/604.
Need to reproduce this. It was discovered by a user (who?) in load testing.
Which study + tree?