Re: Problems with Seamonkey 2.35a2

Hi Dave

Dave Yeo wrote:
> Peter Brown wrote:
>> Hi All
>>
>> I have been using this build for a couple of weeks and have noticed
>> several problems:
>>
>> 1] Sometimes Seamonkey does not close/exit properly - Seamonkey is not
>> onscreen, not on the Windows list but when trying to start it a message
>> appears onscreen that Seamonkey is already running but not responding.
>> Sure enough, there it is in the Process list. Checking the Process list
>> shortly after closing/exiting Seamonkey does sometimes show Seamonkey
>> still running. I have tried to spot a possible reason and suspect Flash
>> as every time Seamonkey does not close/exit properly Flash has been in
>> use.
>
> I've only seen similar a couple of times without Flash.
> I thought there was now code to catch a hung exit and kill the browser.
> May not be enabled on SM though or just broken.
> I'll note a discussion on mozilla.dev.platform put crashes at exit close
> to the top crash with out of memory (OOM) errors another top crasher.
> The OOM crashes are often due to fragmented memory and the browser not
> being able to allocate a big enough chunk.
> These would be referring to FF46 or so.
>
>>
>> I gather that Flash is not recommended as a plugin with this build of
>> Seamonkey but have no idea what to use to play Flash video when the
>> libav support files cannot handle Flash playback.
>
> Flash is known to be broken with recent releases and the developers have
> no interest in fixing.
> You might be able to present the browser as a mobile version (where
> there is no Flash) to encourage sites to offer a Webm version of a video.
>
>>
>>
>> 2] Seamonkey sometimes fails to start "cleanly": Seamonkey appears
>> onscreen, the Sidebar bookmarks get populated the cursor stops flashing
>> on the url entry line and Seamonkey has crashed. Killing that instance
>> of Seamonkey and restarting usually works OK. No idea on possible causes
>> as this happens even if Seamonkey is the 1st app run after system
>> startup as well as when the system has been up and running for a while.
>>
>>
>> Any thoughts on possible resolutions to the above?
>
> Haven't seen that one. Possibly profile corruption
> Dave
>


I guess it could be Profile corruption - but if it was surely the 
problem would persist and further attempts to start SM would have the 
same result.

Having just had 1 of these instances the only thing that I can add at 
the moment is that the cursor is showing as a timer when positioned over 
SM - probably indicating that something is not loading.

Just a thought: is Flash initialised at SM start? If "Yes" could that be 
the culprit?


Regards

Pete