Bug reporting

Thanks much to Brent Simmons for reporting a memory leak in WebKit. I can’t speak for the Safari team, of course, but external bug reports — particularly ones with reproducible simple test cases, like this one — are always appreciated.

In the comments on Brent’s message, Mike Zornek said this:

    I report bugs when I can but the biggest thing I want is a Cocoa app to do it in. I mean reentering the same info, bug after bug is so tedious. (Let me save the info on my hardware so I don’t have to reenter it every time!)

Yep; it’s tedious, and that’s a shame. That’s why I used to keep a saved System Profiler report around — I’d just paste it into the web site and be done with it. I also started to write an app to provide a more usable front end to Apple’s bug reporter once upon a time but stopped when I couldn’t find a good way to do HTTPS. There are much better APIs for that these days, so writing something like that shouldn’t be too hard any more. I don’t know what Apple management would think, but I’m sure a lot of developers would find an app like that useful if someone were to write one.

1 Comment

  1. rentzsch Said,

    July 29, 2003 @ 5:38 pm

    What’s really annoying is that RadarWeb is a WebObjects application, and WO (circa 5.2) has fantastic SOAP support built-in. Likewise, Mac OS X has a SOAP stack. Assuming RadarWeb is a WO5.2 app, turning around a version 1.0 bug entry app is literally like 16 work hours, including both frontend and backend.

RSS feed for comments on this post