[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Robot.createScreenCapture VM crash

Subject: Re: Robot.createScreenCapture VM crash
From: Elliott Hughes <email@hidden>
Date: Tue, 12 Jul 2005 23:17:26 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden

On 2005-07-12, at 22:45, Hsu wrote:

On Jul 12, 2005, at 8:54 PM, Elliott Hughes wrote:
i do have a problem with the system, though. it's terrible. and that's something that Apple's developers should try to fix, because it reflects badly on you.

If you haven't filed bugs on them, we don't know about them. We live and breathe by what's filed in Radar (the bug tracking system).

by "system", i meant the "bug tracking system". not Mac OS or its Java implementation.

comment or suggest work-arounds, other developers can. in a case like my Robot.createScreenCapture crash, i can submit a bug *and* warn other developers *and* tell other developers about my work- around, all at the same time --- but only if it's a Sun problem rather than an Apple one.

With Apple it takes 2 steps. One to post to java-dev, and another to file a bug. I understand it's quite annoying, but I don't have any control over that aspect. I _can_ tell you that filing a bug report is the _only_ guaranteed way to make sure an engineer looks at it, even if that's only to say "it's a duplicate of XX".

it's not filing the report that's annoying per se. it's that filing a bug report feels like throwing information into a black hole. and Apple developers have more control over that than outsiders do.

things are especially bad in the common case where a defect is marked as a duplicate. if you didn't submit the original, that's it: complete silence from then on.

This is something to take up with developer relations; I'd agree that it would be nice to track at least the status of the duplicate bug.

i and others have made these complaints many times, in many places. including mailing developer relations.

nothing's improved since i bought a PowerBook in 2001.

i think the statuses outsiders see are bogus, too. they seem to be static until just after a major release, at which point some subset will change. if you don't get mail within a couple of weeks after a paid-for OS release, you know it won't fix your bug.

and of course, you can't search for duplicates beforehand.
This is likely to be intentional, the more duplicates that are filed, the more likely the bug will be fixed.

that's a very weak argument. it's a rationalization for the current solution, yes, but it's not valid to conclude that "lack of search" is a necessary feature of all solutions that provide developer- influenced priority.

I think the intent is to try to only point out things that are generally relevant to you as a developer. Lots of radar #s followed by the explanation "we crash less" or "we are faster" aren't so useful. Nor is listing all the duplicate or related bugs - the "AWT threading" bug, for instance, covered 100+ unique radars.

you're wrong. Sun publish the lists of fixed bugs with links to the bug's page, and it's *immensely* useful. especially when the page says "fixed in x.y.z, work-around is:".

I'm trying to tell you that filing a bug _will not be a waste of your time_. It is the _only_ guaranteed way to let Apple know about a bug.

it is a waste of my time if i have an acceptable work-around, as i do here.

i'd much rather waste my time trying to get the (bug tracking) system fixed. it's a lot taller order, but it would have a much bigger effect than fixing Robot.createScreenCapture ever could.

 --elliott

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden

References:
	>Robot.createScreenCapture VM crash (From: Elliott Hughes <email@hidden>)
	>Re: Robot.createScreenCapture VM crash (From: Hsu <email@hidden>)
	>Re: Robot.createScreenCapture VM crash (From: Elliott Hughes <email@hidden>)
	>Re: Robot.createScreenCapture VM crash (From: Hsu <email@hidden>)
	>Re: Robot.createScreenCapture VM crash (From: Elliott Hughes <email@hidden>)
	>Re: Robot.createScreenCapture VM crash (From: Hsu <email@hidden>)

Prev by Date: Re: setLocation before setVisible on multiple displays
Next by Date: Re: Topic: Tiger 10.4.1, Java 1.5 and IntelliJ IDEA 4.5.4 crashes
Previous by thread: Re: Robot.createScreenCapture VM crash
Next by thread: Re: Robot.createScreenCapture VM crash
Index(es):
- Date
- Thread

Home