Yes, it has to do with Safari's limited call stack and memory issues. In other words, it can't handle such large amounts of js. I usually test each module at a time in Safari.
-- Brandon Aaron On 9/27/07, ravenel <[EMAIL PROTECTED]> wrote: > > > Is this a known problem? > >
