Anton, disable the garbage collection and you might get another error message which is sometimes more descriptive of the real problem...
really, I've tried this a few times and I was suprised by the suddenly meaningfull error I got. I guess it depends on the error itself. -MAx --- "You can either be part of the problem or part of the solution, but in the end, being part of the problem is much more fun." > -----Original Message----- > From: Anton Rolls [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 11, 2003 8:49 AM > To: [EMAIL PROTECTED] > Subject: [REBOL] Re: crash: root block overflow > > > > It wasn't due to using wait (after an hour > of reorganising code later..) > I implemented time events to divide the work > and the problem still occurs. > (Actually, that triggers a memory about too many > events stacking up causing a crash...?) > > My next theory is that it is something to > do with trying to read a file that another > process is writing to, because that's exactly > what my process does, polls a log file written > to by another installer to see when a response > code is written. > I hear a bell tinkling from a recent thread, > but we'll just see... > > Anton. > > > Has anyone had this crash before? > > and what does it mean? > > > > Crash! Root block overflow > > > > The most recent dodgy thing I did was put a wait inside > > an action block. I'm only waiting 1 second or so, though. > > > > That's probably it actually. > > I'll try make it using time events. > > > > Anton. > > -- > To unsubscribe from this list, just send an email to > [EMAIL PROTECTED] with unsubscribe as the subject. > > -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
