Activity log for bug #357907

Date Who What changed Old value New value Message
2009-04-08 18:47:36 Björn Tillenius bug added bug
2009-04-08 18:48:05 Björn Tillenius tags performance timeout
2009-04-08 18:49:48 Björn Tillenius description 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. 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
2009-04-08 21:36:09 Martin Olsson description 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 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.
2009-04-08 21:38:48 Martin Olsson malone: status New Confirmed
2009-08-21 17:27:46 Graham Binns malone: status Confirmed Triaged
2009-08-21 17:27:49 Graham Binns malone: importance Undecided High
2009-08-21 17:27:54 Graham Binns malone: milestone 2.2.8
2009-08-21 17:43:38 Graham Binns malone: assignee Graham Binns (gmb)
2009-08-27 18:49:33 Deryck Hodge malone: milestone 2.2.8 3.0
2009-09-15 14:42:46 Deryck Hodge malone: milestone 3.0 3.1.10
2009-10-20 15:16:50 Graham Binns malone: status Triaged In Progress
2009-10-22 10:15:52 Graham Binns malone: status In Progress Triaged
2009-11-02 11:52:54 Graham Binns malone: milestone 3.1.10 3.1.11
2009-11-25 14:26:39 Deryck Hodge malone: milestone 3.1.11
2009-12-11 16:13:28 Graham Binns malone: assignee Graham Binns (gmb)
2010-01-11 11:17:22 Graham Binns malone: assignee Graham Binns (gmb)
2010-01-11 14:38:47 Graham Binns malone: status Triaged In Progress
2010-01-27 11:32:35 Graham Binns malone: status In Progress Triaged
2010-01-27 11:32:35 Graham Binns malone: assignee Graham Binns (gmb)
2010-07-25 08:07:12 Robert Collins tags performance timeout timeout
2010-08-10 01:29:19 Robert Collins malone: status Triaged Fix Released