Comment 8 for bug 87638

Sorry, I missed this problem the other when I logged one similar to this. Bug# 95822 is the one I opened up. You can look at the detail that I provided, but to reiterate my bug report, there does seem to be a file size limitation.

I generated a massive firefox crash report (approximately 120Mbytes). If I tried to send that one up either manually or as part of the apport reporting system I would receive the internal 500 error. Since the developer only needed the CoreDump from this report, because he got everything else I took that file and tried to send it. I got at error there too. The file size was just over 90 Mbytes.

When I changed the way I was compressing the file I got it down to about 85 mbytes in size. This one could then be uploaded properly. Any file size over 90 Mbytes seemed to fail for me, so some part of the transport is putting in a limit to what can be uploaded...

I hope this help a little bit, bit I can confirm this problem with a little more anecdotal information of my own.... Good Luck.