Our customers do not give us the luxury of waiting for 2 to 3 years
to turn around critical bugs. I really am surprised that you consider
it reasonable to expect users to live with plugins that might be
scribbling over memory and causing random crashes and so forth for
such a period of time.
Hmmm yeah, to give a "real world example", two of my Destroy FX AUs failed
validation with the auval update in 10.4.9 (my bad, I guess I forgot to
run those ones through the auval seeds; sometimes I only remember to do
the ones that I get paid for cuz I'll have someone on me about those).
They failed cuz, under certain circumstances, they will write into memory
out of bounds. Doesn't seem like such a bad thing to me that auval has
added more ways to catch this. My plugs doing this sort of thing, that's
pretty bad news. Of course they were only doing it cuz of a rather
esoteric bug in the AU SDK rdar://5067220 heh heh, but none-the-less,
bad stuff for a plugin to be doing...
Sophia
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
