FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

BugScout limitation on data size

I've been working with bugscout (the .net version right now)... and I'm wondering if there is some basic size limit on the amount of info it can send up to the server.

I've outfitted it to return much more info about the hardware of the user's machine and user comments about the crash.  But some of that just seems to get lost.  Not sure if its a limitation or me.

-- David
David Whatley Send private email
Friday, March 4, 2005
How much is a lot?

I'm pretty sure IIS has a limitation of about 100K on each field in an HTTP POST, so that's one hard limit I can think of. There may be something else I'm not thinking of.
Joel Spolsky Send private email
Saturday, March 5, 2005
I don't think I'm near 100K in my case that's losing data.  But it does make me wonder if there might be a better way to transfer this data to the server than a query string.  Something in the back of my head is nagging me about limitations... just can't recall what it was.

The biggest problem I've found with BugScout is that it doesn't seem to catch everything.  If I throw an exception (by hand), it catches that just fine.  But there are tons of other crashes that just go right past it that I don't understand.

Like one today where the user got:

Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.

Process id = bla bla  Thread id = bla bla

But it never got caught.  In this case it even says it was a CLR exception.  So I don't get why I didn't catch the dang thing.

I'm doing this sorta thing before my application main loop:

      Application.ThreadException += new ThreadExceptionEventHandler(eh.OnThreadException);

ThreadException claims to be the event raised when an unhandled exception occurs.  Works when I purposely throw one.

The other extenuating circumstance, so to speak, is that my C# .NET managed code calls into unmanaged code (in the form of a DLL).  It has a very wide interface (lots of functions).  Is it possible that exceptions thrown there will not be caught?  If so, is there something I can do to catch these?  Do I have to rig up the ActiveX version of BugScout as well as the .NET version?

-- David
David Whatley Send private email
Saturday, March 5, 2005

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.