On Fri, 8 Aug 2008 14:36:48 -0600, Michal Jaegermann wrote:
With a "new-and-improved" bugzilla finding an existing bug
seems
to border with a miracle. "Quick search" produces something,
mostly irrelevant stuff, without any apparent order.
If you will try "Edit Search" (or to use "Advance Search" - which
goes down to the same) then upon picking up something like
"Fedora" for a "Product:" this page goes catatonic for a long
time and after that I am regalled with an alert which says:
A script on this page may be busy, or it may have stopped
responding. You can stop the script now, or you can continue to see
if the script will complete.
If I will try to continue then another alert of that sort will
show up. "Stop" just stops everything and while you can get out
of there you cannot find anything at all.
In Firefox, open "about:config", filter for "script", then
increase the dom.max_script_run_time value to 60 seconds or so.
With the older bugzilla, one also encountered those time-outs when
using machines with less than 2 GHz clock rates. With the new bugzilla,
the requirement for processor power has increased a lot.