Sometimes +filebug times out when processing a blob. Almost all time is spent in Python, so it could be that the processing of the blob is inefficient. I haven't looked at exactly where the problem lies.
An example OOPS is OOPS-1194D3715, and the crash report it was processing is here: devpad.canonical.com:oops-1194D3715.crash
In particular this affects automatic crash reports submitted through apport. For example, whenever Firefox crashes with above a certain number of TABs open the crash dump is always big enough to cause a timeout while submitting to launchpad. To properly gauge the impact of this bug, please consider the fact that critical crash bugs in several Ubuntu applications (most notably Firefox) are not being submitted because of this issue. As a workaround, it's possible to select "Reduced crash report" in the apport UI but then I don't the the apport retracers will be able to recover the stacktrace and so it's important that the user experiencing the crash had previously installed the debug symbols for Firefox on this machine.
I would appreciate if you increased (or at least considered increasing) the importance/priority of this bug.