My main issue here is hangs, NOT crashes. Crashes I'll take if they are not in NPOJI6.DLL
We are getting a lot of hangs that are ending up being Java hangs. If you find a page that hangs consistently, remove Java and see if it still hangs. Mike Kaply IBM Mikus Grinbergs wrote: > On Thu, 08 Nov 2001 13:18:09 -0600 Michael Kaply ><[EMAIL PROTECTED]> wrote: > > If you find a hang in Warpzilla PLEASE test it WITHOUT Java. > > > > We need to know whether the hang is a Warpzilla hang or a Java hang. > > > > If I see bugs that are opened as hangs without explicitly saying that > > Java was NOT involved or the page that hangs has Java on it, I will mark > > the bug INVALID. > > > > My team does not own the Java plugin and we can't fix bugs in it. > > > > Mike Kaply > > IBM > > I realize that the team working on Warpzilla has finite resources. > But so do users. > > I think that a request to not submit hangs which occur in \java13 > (or in npoji6.dll) is perfectly legitimate, if you don't own those. > > But what does "If you find a hang in Warpzilla PLEASE test it WITHOUT > Java" mean ? Why are you saying that bugs will be marked INVALID if > the page that hangs has <EMBED> html somewhere, __whether or not__ > Preferences -> Advanced -> Enable Java was *disabled* at the time ? > > Suppose a crash occurs in xpcom.dll. Are you *really* asking the user > to examine ALL the received html (e.g., in Warpzilla's memory and disk > caches) to certify that "Java was not involved" ?? > > mikus
