My SeaMonkey loves to crash in my decade old, 64-bit W7 HPE SP1 PC with @ xul.dll | mozglue.dll | xul.dll | mozglue.dll | xul.dll | GetUpdateRect.

[Ant]

Hello.

My SeaMonkey loves to crash from xul.dll in my decade old, 64-bit W7 HPE
SP1 PC once in a while. Here are a few sent crash reports:

https://crash-stats.mozilla.org/report/index/20cc3419-007d-4e9c-b208-333ad0200530

https://crash-stats.mozilla.org/report/index/16e81e6a-e0b7-45ed-9e93-fbb740200606

https://crash-stats.mozilla.org/report/index/90271966-1928-4524-bf7e-ac5230200514

It happens once in a while though. It doesn't matter how long
SeaMonkey's uptime was. Is anyone else getting thes XUL.dll crashes too
or just me?

Thank you for reading and hopefully answering. :)
--
..!.. *isms, sins, devil, illness (e.g., COVID-19/2019-nCoV/SARS-CoV-2),
etc.
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ http://aqfl.net & http://antfarm.ma.cx /
/ /\ /\ \ http://antfarm.home.dhs.org
| |o o| | Axe ANT from its address if shown & e-mailing privately.
\ _ / Please kindly use Ant nickname & URL/link if crediting.
( )

[Ant]

I guess it's only me?
https://crash-stats.mozilla.org/report/index/632c79c9-89c6-471e-91b4-42d9a0200614
as of a few minutes ago. :(

On 6/5/2020 7:40 PM, Ant wrote:
> Hello.
>
> My SeaMonkey loves to crash from xul.dll in my decade old, 64-bit W7 HPE
> SP1 PC once in a while. Here are a few sent crash reports:
>
> https://crash-stats.mozilla.org/report/index/20cc3419-007d-4e9c-b208-333ad0200530
>
>
> https://crash-stats.mozilla.org/report/index/16e81e6a-e0b7-45ed-9e93-fbb740200606
>
>
> https://crash-stats.mozilla.org/report/index/90271966-1928-4524-bf7e-ac5230200514
>
>
> It happens once in a while though. It doesn't matter how long
> SeaMonkey's uptime was. Is anyone else getting thes XUL.dll crashes too
> or just me?
>
> Thank you for reading and hopefully answering. :)--

--
Life is so crazy! ..!.. *isms, sins, (d)evil, illness (e.g.,
COVID-19/2019-nCoV/SARS-CoV-2), deaths, heat waves, arsonists,
out(r)ages, unlucky #4, 2020, etc. :(

[Frank-Rainer Grahl]

Ant wrote:
> I guess it's only me?
> https://crash-stats.mozilla.org/report/index/632c79c9-89c6-471e-91b4-42d9a0200614
> as of a few minutes ago. :(
>
>
> On 6/5/2020 7:40 PM, Ant wrote:
>> Hello.
>>
>> My SeaMonkey loves to crash from xul.dll in my decade old, 64-bit W7 HPE SP1
>> PC once in a while. Here are a few sent crash reports:
>>
>> https://crash-stats.mozilla.org/report/index/20cc3419-007d-4e9c-b208-333ad0200530
>>
>>
>> https://crash-stats.mozilla.org/report/index/16e81e6a-e0b7-45ed-9e93-fbb740200606
>>
>>
>> https://crash-stats.mozilla.org/report/index/90271966-1928-4524-bf7e-ac5230200514
>>
>>
>> It happens once in a while though. It doesn't matter how long SeaMonkey's
>> uptime was. Is anyone else getting thes XUL.dll crashes too or just me?
>>
>> Thank you for reading and hopefully answering. :)--

This is in the taskbar preview code. I am sure this is the crash you mentioned
some time ago. The bug is still open for Firefox.

https://bugzilla.mozilla.org/show_bug.cgi?id=1277167

I put a fix for Bug 1485253 into 2.53.2 because of it but it seems not to help :(

https://bugzilla.mozilla.org/show_bug.cgi?id=1485253

I am not sure what triggers it in your config. I am running Windows 7 too and
never occurs here. Are the latest AMD drivers installed? 13.9 I think. Any
toolbar extensions?

Seems Bonjour by Apple is installed which messes with the network and might
causes problmes too.

FRG


FUNC 1e3d3f0 40 0 mozilla::widget::TaskbarPreview::MainWindowHook(void
*,HWND__ *,unsigned int,unsigned __int64,__int64,__int64 *)

1e3d3f0 9 404 276913

1e3d3f9 5 409 276913

1e3d3fe 6 412 276913

1e3d404 9 417 276913

1e3d40d 5 418 276913

1e3d412 7 419 276913

1e3d419 6 421 276913

1e3d41f 9 422 276913

1e3d428 8 426 276913

[Gerry Hickman]

Ant wrote:
> I guess it's only me?
> https://crash-stats.mozilla.org/report/index/632c79c9-89c6-471e-91b4-42d9a0200614
> as of a few minutes ago. :(

Has this only been happening since you moved to SeaMonkey 2.53.2?
I was only Win7 x64 for nearly ten years with no crashes at all, (using
SeaMonkey up to 2.49.x).

You should see a matching event in the application event log, you can
copy and paste it.

xul.dll could mean it's related to a plugin.

--
Gerry Hickman (London UK)

[Paul in Houston, TX]

Ant wrote:
> I guess it's only me?
> https://crash-stats.mozilla.org/report/index/632c79c9-89c6-471e-91b4-42d9a0200614
> as of a few minutes ago. :(
>
>
> On 6/5/2020 7:40 PM, Ant wrote:
>> Hello.
>>
>> My SeaMonkey loves to crash from xul.dll in my decade old, 64-bit W7
>> HPE SP1 PC once in a while. Here are a few sent crash reports:
>>
>> https://crash-stats.mozilla.org/report/index/20cc3419-007d-4e9c-b208-333ad0200530
>>
>>
>> https://crash-stats.mozilla.org/report/index/16e81e6a-e0b7-45ed-9e93-fbb740200606
>>
>>
>> https://crash-stats.mozilla.org/report/index/90271966-1928-4524-bf7e-ac5230200514
>>
>>
>> It happens once in a while though. It doesn't matter how long
>> SeaMonkey's uptime was. Is anyone else getting thes XUL.dll crashes
>> too or just me?
>>
>> Thank you for reading and hopefully answering. :)--

https://www.personalcomputerfixes.com/how-to-resolve-the-firefox-xul-dll-error/

[Ant]

On 6/14/2020 3:24 PM, Frank-Rainer Grahl wrote:
...

> This is in the taskbar preview code. I am sure this is the crash you
> mentioned some time ago. The bug is still open for Firefox.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1277167
>
> I put a fix for Bug 1485253 into 2.53.2 because of it but it seems not
> to help :(
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1485253
>
> I am not sure what triggers it in your config. I am running Windows 7
> too and never occurs here. Are the latest AMD drivers installed? 13.9 I
> think. Any toolbar extensions?

Yes, for the decade old ATI Radeon 4870 video card (512 MB of VRAM).
Here are my current extension according to PrefBar:

Last updated: Sun Jun 14 2020 23:35:33 GMT-0700 (Pacific Standard Time)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0)
Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.2

Extensions (enabled: 6)
* ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
* DOM Inspector 2.0.17.2 (http://www.mozilla.org/projects/inspector/)
* Expire history by days [converted] 1.2.0
* Open With 6.8.6 (https://github.com/darktrojan/openwith)
* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
* uBlock Origin 1.16.4.20
(https://github.com/gorhill/uBlock-for-firefox-legacy)

> Seems Bonjour by Apple is installed which messes with the network and
> might causes problmes too.

My Bonjour service is disabled.

[Ant]

On 6/14/2020 3:28 PM, Gerry Hickman wrote:
> Ant wrote:
>> I guess it's only me?
>> https://crash-stats.mozilla.org/report/index/632c79c9-89c6-471e-91b4-42d9a0200614
>> as of a few minutes ago. :(
>
> Has this only been happening since you moved to SeaMonkey 2.53.2?
> I was only Win7 x64 for nearly ten years with no crashes at all, (using
> SeaMonkey up to 2.49.x).

I think it started with v2.53. I don't recall earlier versions doing it.

> You should see a matching event in the application event log, you can
> copy and paste it.
>
> xul.dll could mean it's related to a plugin.

The only plugin in SM is:
Shockwave Flash

File: NPSWF64_32_0_0_387.dll
Path: C:\Windows\system32\Macromed\Flash\NPSWF64_32_0_0_387.dll
Version: 32.0.0.387
State: Enabled
Shockwave Flash 32.0 r0

MIME Type Description Suffixes
application/x-shockwave-flash Adobe Flash movie swf
application/futuresplash FutureSplash movie spl


It is rarely used too since very few web sites use them. I also have SM
to ask me to manually run or not.

[Don Spam's Reckless Son]

Quoting from that link,
> The first step you should take is to reinstall FireFox. This is very easy to do but does hold the risk of losing some of your personal data.

I could not see anything on that page to indicate when it was written,
but the claim that reinstalling Firefox could cause damage to the
profile is . . unusual. By that logic, installing a new version can
also damage the profile.
Ok, that sort of applies when moving from 2.49.x to 2.53.x but that only
affects the ability to fall back.
(The page source says "This site is optimized with the Yoast SEO plugin
v14.3", that is the current level)

--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/

[Frank-Rainer Grahl]

Ant wrote:
> On 6/14/2020 3:28 PM, Gerry Hickman wrote:
>> Ant wrote:
>>> I guess it's only me?
>>> https://crash-stats.mozilla.org/report/index/632c79c9-89c6-471e-91b4-42d9a0200614
>>> as of a few minutes ago. :(
>>
>> Has this only been happening since you moved to SeaMonkey 2.53.2?
>> I was only Win7 x64 for nearly ten years with no crashes at all, (using
>> SeaMonkey up to 2.49.x).
>
> I think it started with v2.53. I don't recall earlier versions doing it.
>

Wouldn't wonder me. Lots of new code.

I am not sure if the expire history by days ext still works ok but it should
not cause it. This is taskbar preview code and so more on the Windows level.

If this is still the original Win 7 installation I would check for cruft. Old
Apple stuff. Preinstalled junk and so on. Virus scanner might also be
responsible.

Mostly on 8.1 now but 7 is very stable for me in a vm and also on the test
systems. I am using astandard aero theme. So I just suspect something
external or hardware related. But probably another software not up to date.

FRG

[Ant]

Oh well, I will have to live with it. Thanks God for restore sessions! I
hope all my sent crash reports help to investigate and fix. I also use
the (new/lat)est Firefox, but not that much and haven't seen this issue
happen yet(?).

[Paul in Houston, TX]

I think the procedure is written for non computer literate folks.

[Frank-Rainer Grahl]

Ant wrote:
> On 6/15/2020 6:27 AM, Frank-Rainer Grahl wrote:
>> Ant wrote:

>>
>> Mostly on 8.1 now but 7 is very stable for me in a vm and also on the test
>> systems. I am using  astandard aero theme. So I just suspect something
>> external or hardware related. But probably another software not up to date.
>
> Oh well, I will have to live with it. Thanks God for restore sessions! I hope
> all my sent crash reports help to investigate and fix. I also use the
> (new/lat)est Firefox, but not that much and haven't seen this issue happen
> yet(?).

They have later blacklisting tech in. Might be that a dll is just blocked
here. I need to look into it for later releases.

A few of issues which came up in the crash reports should be fixed in 2.53.3.
I frequently check and if I identify something put in the fix.

FRG

[Ant]

Those crash report issues weren't mine, right?

[Frank-Rainer Grahl]

Ant wrote:
> On 6/15/2020 2:01 PM, Frank-Rainer Grahl wrote:
>>
>>
>> Ant wrote:
>>> On 6/15/2020 6:27 AM, Frank-Rainer Grahl wrote:
>>>> Ant wrote:
>>
>>>>
>>>> Mostly on 8.1 now but 7 is very stable for me in a vm and also on the test
>>>> systems. I am using  astandard aero theme. So I just suspect something
>>>> external or hardware related. But probably another software not up to date.
>>>
>>> Oh well, I will have to live with it. Thanks God for restore sessions! I
>>> hope all my sent crash reports help to investigate and fix. I also use the
>>> (new/lat)est Firefox, but not that much and haven't seen this issue happen
>>> yet(?).
>>
>> They have later blacklisting tech in. Might be that a dll is just blocked
>> here. I need to look into it for later releases.
>>
>> A few of issues which came up in the crash reports should be fixed in
>> 2.53.3. I frequently check and if I identify something put in the fix.
>
> Those crash report issues weren't mine, right?

I think one of them mentioned in this group. Not sure. No way to identify the
reports. Would need to check the previous threads.

FRG

[Ant]

On 6/15/2020 3:37 PM, Frank-Rainer Grahl wrote:
...

>>> They have later blacklisting tech in. Might be that a dll is just
>>> blocked here. I need to look into it for later releases.
>>>
>>> A few of issues which came up in the crash reports should be fixed in
>>> 2.53.3. I frequently check and if I identify something put in the fix.
>>
>> Those crash report issues weren't mine, right?
>
> I think one of them mentioned in this group. Not sure. No way to
> identify the reports. Would need to check the previous threads.

Hmm, I wonder if I should upgrade to v2.53.3 beta to replace my v2.53.2
soon instead of waiting for its final release. Is it stable enough for
production usage? ;)
--
:) Picard Day!