On Wed, Jun 20, 2012 at 6:48 AM, Eric Ayers <[email protected]> wrote:
> Now, the problem with diagnosing this is that the file is set to be > deleted on exit. So after the program exits, you can't see how > ridiculously huge the file might have been. To test that theory, you > could try commenting out this line to test it, or you could keep track > of the # of bytes written and spit it out when this exception occurs. Isn't there a way to disable this with a system property or command-line flag? -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
