Our current release (Sprint No. 37 since we moved to a Scrum methodology!) is focused on bug bashing: mostly server-related bugs, and a few that users might have observed themselves.
This is fairly typical of our development cycles: while we fix major bugs in every release, every once in a while we spend an entire release on just general bug bashing and cleanup. These offer opportunities to catch up on infrastructure improvements, getting our test cases in better shape and other administrative work.
Release 37 should be done, with testing, by the end of the week: it will have about 65 work items completed, with another 21 items that were trashed.
Trashed items are usually duplicates of bugs: different symptoms with the same underlying cause.