What about acrobat? You weren't by chance using that, were you?
Alan Beagley wrote:
> I think I am onto something -- but it may take a while to figure things
> out:
>
> Mozilla hung again yesterday when I exited. Later I started killing
> running processes just by doing RMB -> "Close" on the Task List (in
> which the "hung" Mozilla thread did not show). Unfortunately I didn't
> check the Process Commander process list after closing *each* process,
> but after closing everything but the Desktop, the previously "hung"
> Mozilla process had disappeared as well, so perhaps some other process
> was stopping Mozilla from closing properly?
>
> The processes that were running were:
>
> 1. Siegfried Hanisch's ancient ScreenSaver 2.6
>
> 2. PMFax
>
> 3. XCenter (part of XWorkPlace, ver. 0.9.20)
>
> 4. UPSMonitor B ver. 1.2c (but I've only recently started using this
> program, and I had the unkillable Mozilla threads before that)
>
> 5. LCDClock (a multi-time-zone digital clock)
>
> 6. SmartCache ver. 0.75 (a proxy server using Java).
>
> Now I just have to wait for Mozilla to hang again (if it does -- I don't
> have SmartCache and LCDClock running at present) and see which program,
> when closed, allows Mozilla to close.
>
> -=-
> Alan
>
>
>
> Michael Kaply wrote:
>
>> Did you use an existing profile? Or create a new one?
>>
>> Alan Beagley wrote:
>>
>>> To clarify: One of the points I am trying to make here is that
>>> Mozilla's defaults leave it wide open to being brought down by nasty
>>> or just-plain-flaky messages or Web pages.
>>>
>>> Another is that even a clean install (with no remnants of earlier
>>> versions of Mozilla or of the IBM-branded browser or of Netscape to
>>> confuse it) of a supposedly stable release can get its knickers in a
>>> knot when one tries to exit.
>>
>
