Steps to reproduce:

1. create a web widget - don't limit by any host groups
2. Navigate to screen title...
3. Click on screen element...
4. ...

Result:
will cause the database cpu to peg, primarily user cpu
Expected:
that a dashboard with web widget doesn't cause a CPU pegging situation

I was able to find all my dashboards where we weren't limiting it by hostgroup and thankfully was able to add a limit, but we hadn't experienced this in 6.0.4 

I'm not sure what would make sense to provide as far as debugging information.   The one host group I was able to run this with has 1070 web scenarios, and it took a while to load, but it was able to load.