Is there a workaround for crash when user selects too many files with browseForOpenMultiple?

Thanks for the link, but actually, it's not "me" that is trying to select (not "read") everything all at once -- it's my eventual users when I release the program who will need to limit themselves from doing so, and it would be nice if there was a way to "fail gracefully" and simply tell them they've tried to select (NOT read!) too many files at one time.  If there were a precise number, I suppose I could at least warn them of that, but apparently it's not a set amount; it seems to depend on the character length of the directory structure.  The program does not time out (the problem addressed in the link you provided), it simply exits.  The only workaround I've come up with is to build my own file selection picker, and not use browseForOpenMultiple at all, which is what I'm constructing right now.  But that's a shame to have to do that, since, ideally, the OSs all already have one that should work perfectly well, with thumbnails, size, date of last modification, etc. already displayed.  And it's what the users are used to using. Flash shouldn't just crash.

Thanks for your reply, but unfortunately I'm doing those things already, but it still crashes the player if I try to select too many files at once.