Thank to all for the given information. After a lot of research and thinking, we could find the conditions which causes the crash.
Our system is a "Computer Based Assessment" system, which allows us to submit persons to psychotechnical tests. One of those test is composed of a screen displaying 9 images, which stays visible during 5 sec. The person must choose one of those images by clicking it. After the delay, the screen desippear and a new screen is displayed. We noticed that, when a person clicks outside the image-button and hold the mouse button depressed, and the limit of 5 sec is reach, the other screen is constituted and the application crashes. Our conclusion is:=20 Holding the mouse button creates an event which is queued for handling. When the new screen is composed, a 'feel+engage event is triggered, for the chronometer. When rebol starts this event, some mouse-event remaining from the previous screen was not completely handled and causes the crash. What we think to do: Before the new screen is composed and displayed, first "flush" the event queue for cleaning the old mouse event that remains. Does it make sense ? And how could we achieve this ? I am not aware of a clear-events instruction, and a 'do-events just brake the system. TIA, --christophe >=20 >=20 > Maybe not of big help to you, but a long time ago I had a=20 > situation like this where 80% of users had no troubles but=20 > the rest kept getting the "Crash (Should not happen)" thing=20 > randomly. I forgot many details, but in essence, I finally=20 > understood that the problem was related to inform (modal=20 > window). The crash would occur when multiple windows were=20 > open (one of which with inform) and the user would insist=20 > clicking on fields in a window that did not have the focus.=20 > It would not happen all the time, but would happen for sure=20 > after a using inform a few times. There were no reasons to=20 > click on the wrong window and most users would not do that,=20 > but some kept on doing it repeatedly... >=20 > Louis >=20 >=20 > At 06:45 AM 2006-01-19, you wrote: >=20 > >Hi list, > > > >Our new system, written with REBOL, is running now on some 150 PC's,=20 > >distributed over 13 different locations through Belgium.=20 > Those PC's are=20 > >using M$ NT, 2000 or XP and we do not have any control over the=20 > >configuration. > > > >In 90% of the cases runs the software without problems. But in some=20 > >case, never the same, never at the same time or in the same=20 > conditions,=20 > >we got an howful "Crash (Should not happend). Corrupt datatype 54 at=20 > >101" -error. > > > >The application is intensively making use of VID. We did=20 > optimalize the=20 > >memory use (after the generation of 430 screens, we only use=20 > some 2MB=20 > >RAM). We do not make use of 'recycle instructions in the code. > > > >Can anybody give us some clue about the conditions that=20 > cause an "Crash=20 > >(Should not happend). Corrupt datatype 54 at 101" -error and=20 > how we do=20 > >have to interpret it ? > > > >TIA, > > > >--christophe > > > >This e-mail and any attachments may contain confidential and=20 > privileged=20 > >information. If you are not the intended recipient, please=20 > notify the=20 > >sender immediately by return e-mail, delete this e-mail and=20 > destroy any=20 > >copies. Any dissemination or use of this information by a=20 > person other=20 > >than the intended recipient is unauthorized and may be illegal. > >-- > >To unsubscribe from the list, just send an email to lists at=20 > rebol.com=20 > >with unsubscribe as the subject. >=20 > -- > To unsubscribe from the list, just send an email to lists at=20 > rebol.com with unsubscribe as the subject. >=20 >=20 > ************************************************************** > ******************* > Your E-mail has been scanned against Potential Virus and=20 > Spyware/Grayware dangers by the MOD BE SECURITY SYSTEMS. >=20 This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
