This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ JDK VERSION : 1.7.7 ] When using the integrated error reporter it should check the filesize *before* it starts the upload. It is quite anoying having to upload a +100M heapdump and after an hour getting a "File too large" error.
Are you talking about an issue tracking support (bugzilla or jira?) or the exception reporter that pops up when an exception in the IDE occurs?
The issue tracker inside the IDE, the specific problem I hit when making the RFE is issue #219962. I'm usure if it shows a webpage or a locally generated form. The compressed heapdump for that case is 133M
while not having the complete error i would guess the message was returned from the bugzilla server and complies to what would be returned by the web interface. There is no way to find out what the attachment size limits are on a specific bugzilla instance so hard to say how to set a hard limit. Maybe a warning message that the file is potentially too big would be enough. corner case -> p4
Such a warning would probable be adequate, it's better better that you have yourself elected to wait an hour and it failes (you were warned!) rather than thinking it works and then it fails... Or perhaps a warning that !This can take long time! and then upload the file to the same type of server as the Hudson builder... Just a thought...