dylan@june.cs.washington.edu (Dylan McNamee) (05/01/91)
While playing with the task/semaphore code I posted on alt.sources.amiga, I
decided to try spawning LOTS of tasks, like more than 240, just to see how
many system resources allocated 256 entry task tables. (My system has
more than 16 to start with.)
Much to my suprise, the system didn't even notice--none were really active
processes, spending most of their time in WaitTOF(). So, I decided to check
them out, just to make sure they were all _really_ there. Suprise! Both
Xoper and ARTM crashed, just because there were more tasks than they expected.
The tasklist example in the Libs & Devices disk gracefully refused to
overflow an array after listing the first 128 entries.
I don't know what the lesson here is, other than to always check your
array bounds, if a user affected input is indexing the array. Oh, and
that the Amiga has no problem with lots-o-tasks.
dylan
--
dylan mcnamee / "I stood there on the sidewalk, Roy Rogers
dylan@cs.washington.edu \/lunchpail in my hand. Then I heard sweet children's
Qua! voices...and I began to understand." Randy Newman