seamonkey crashing often with zonealarm 14

User Help for Seamonkey and Mozilla Suite
Post Reply
LMHmedchem
Posts: 78
Joined: August 31st, 2009, 2:29 pm

seamonkey crashing often with zonealarm 14

Post by LMHmedchem »

Hello,

I have just installed zone alarm 14 and have been trying to get things working with seamonkey. I have the email client working, but the browser does not work well at all.

It opens to my home page, but when I try to navigate to this site, at times I get to the site and at others I get a server not responding page. Sometimes seamonkey just crashes. At the moment I only have a rule to let svchost make outbound connections to the DNS server. Several inbound connections to svchost from DNS have been blocked because my memory is that nothing should have to make an inbound connection. I have typically had svchost set to be allowed to connect to the DNS server, my printer, and I think local host. I have never needed to allow it to connect to anything else. In general, all programs are blocked from connections unless whitelisted. This is much harder to set up on zone alarm than it was on comodo, or even private firewall.

I am not sure why it works sometimes and sometimes does not. I am not having any trouble with firefox at all (59.9.0), and that makes even less sense. I have run extensive malware scans and actually restored the OS from a clean image before I installed zone alarm.

I am using seamonkey 2.46 on windows xp.

LMHmedchem
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: seamonkey crashing often with zonealarm 14

Post by frg »

> I am using seamonkey 2.46 on windows xp.

Try upgrading to 2.49.4. Works fine on XP.

You need to post a crash id. Without knowing where the crash occurs it is somewhat hard to make suggestions.

FRG
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: seamonkey crashing often with zonealarm 14

Post by therube »

Are SeaMonkey & FF using the same rule sets?
Does ZA install any type of Plugin or Extension into the browser? (Check Addons Manager.)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
LMHmedchem
Posts: 78
Joined: August 31st, 2009, 2:29 pm

Re: seamonkey crashing often with zonealarm 14

Post by LMHmedchem »

frg wrote:Try upgrading to 2.49.4. Works fine on XP.
I will certainly do that but I think the issue is with zone alarm since I had no issues with private firewall yesterday before the switch.
frg wrote:You need to post a crash id. Without knowing where the crash occurs it is somewhat hard to make suggestions.
I have included two mozilla crash reports at the bottom of the post.
therube wrote:Are SeaMonkey & FF using the same rule sets?
There really aren't any significant rules at this point. I set Seamonkey as a trusted application and set if for "allowed" for inbound and outbound internet and trusted zone. I haven't configured any expert rules yet. ZA seems much harder to set up than comodo was. As for firefox, I have entered in the application management panel several times but it keeps vanishing from the list so I have no idea what it's current settings are.
therube wrote:Does ZA install any type of Plugin or Extension into the browser? (Check Addons Manager.)
There is nothing new in the addons manager.

Firefox has some issues as well in that sometimes it can't seem to find a server. I got to this site fine, but for about an hour I couldn't log in. Google results are hit or miss. After following a link to a listed site I often I get a message that the server can't be found. If I then reload the page, it loads fine.

I'm not very impressed with ZA at this point.

LMHmedchem

crash conditions,
seamonkey worked ok and then crashed when closing the application

Code: Select all

AdapterDeviceID: 0x0162
AdapterDriverVersion: 6.14.10.5398
AdapterSubsysID: 00000000
AdapterVendorID: 0x8086
Add-ons: %7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:2.46,uBlock0%40raymondhill.net:1.13.8,%7B73a6fe31-595d-460b-a920-fcc0f8843232%7D:5.1.8.4,https-everywhere%40eff.org:2018.2.26,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.0.8
AvailablePageFile: 6441267200
AvailablePhysicalMemory: 2218541056
AvailableVirtualMemory: 1627525120
BIOS_Manufacturer: American Megatrends Inc.
BlockedDllList: 
BreakpadReserveAddress: 88735744
BreakpadReserveSize: 67108864
BuildID: 20161213183751
CrashTime: 1534051522
EMCheckCompatibility: true
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
GraphicsCriticalError: |[0][GFX1]: Potential driver version mismatch ignored due to missing DLLs 0.0.0.0 and 0.0.0.0 (t=25.6152) 
InstallTime: 1492790905
Notes: FP(D000-L10010-W00000000-T0000) AdapterVendorID: 0x8086, AdapterDeviceID: 0x0162, AdapterSubsysID: 00000000, AdapterDriverVersion: 6.14.10.5398
D2D1.1? D2D1.1- D3D9 Layers? D3D9 Layers+ 
ProductID: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
ProductName: SeaMonkey
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 18099
StartupTime: 1534049477
SystemMemoryUsePercentage: 35
Theme: classic/1.0
Throttleable: 1
TotalPageFile: 7457308672
TotalPhysicalMemory: 3440480256
TotalVirtualMemory: 2147352576
URL: 
UptimeTS: 7329.1183874
Vendor: Mozilla
Version: 2.46
Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 2 : 1 : 6 : 0x20066 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
 MSAFD Tcpip [UDP/IP] : 2 : 2 : 2 : 17 : 0x20609 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
 MSAFD Tcpip [RAW/IP] : 2 : 2 : 3 : 0 : 0x20609 : 0xc : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
 RSVP UDP Service Provider : 6 : 2 : 2 : 17 : 0x22609 : 0x8 : %SystemRoot%\system32\rsvpsp.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
 RSVP TCP Service Provider : 6 : 2 : 1 : 6 : 0x22066 : 0x8 : %SystemRoot%\system32\rsvpsp.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{1268D6E9-BAA1-4949-BBE9-23C63C9877E2}] SEQPACKET 0 : 2 : 17 : 5 : -2147483648 : 0x2000e : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{1268D6E9-BAA1-4949-BBE9-23C63C9877E2}] DATAGRAM 0 : 2 : 17 : 2 : -2147483648 : 0x20209 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{42FA7B62-7667-4713-A1D8-DF608F41DFE3}] SEQPACKET 1 : 2 : 17 : 5 : -1 : 0x2000e : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{42FA7B62-7667-4713-A1D8-DF608F41DFE3}] DATAGRAM 1 : 2 : 17 : 2 : -1 : 0x20209 : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{77AA4D22-EE55-471B-9D5A-E519CB7934F1}] SEQPACKET 2 : 2 : 17 : 5 : -2 : 0x2000e : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{77AA4D22-EE55-471B-9D5A-E519CB7934F1}] DATAGRAM 2 : 2 : 17 : 2 : -2 : 0x20209 : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{A9D3D48F-DA87-4669-821B-A10D668EFE4F}] SEQPACKET 3 : 2 : 17 : 5 : -3 : 0x2000e : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{A9D3D48F-DA87-4669-821B-A10D668EFE4F}] DATAGRAM 3 : 2 : 17 : 2 : -3 : 0x20209 : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192
useragent_locale: en-US

This report also contains technical information about the state of the application when it crashed.
crash conditions,
opened seamonkey to email, worked fine
opened browser to home page, worked fine
entered google search search term, seamonkey crashed

Code: Select all

AdapterDeviceID: 0x0162
AdapterDriverVersion: 6.14.10.5398
AdapterSubsysID: 00000000
AdapterVendorID: 0x8086
Add-ons: https-everywhere%40eff.org:5.1.5,%7B73a6fe31-595d-460b-a920-fcc0f8843232%7D:2.9.0.10,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:2.46,uBlock0%40raymondhill.net:1.6.6
AvailablePageFile: 6397431808
AvailablePhysicalMemory: 2174271488
AvailableVirtualMemory: 1604259840
BIOS_Manufacturer: American Megatrends Inc.
BlockedDllList: 
BreakpadReserveAddress: 88735744
BreakpadReserveSize: 67108864
BuildID: 20161213183751
CrashTime: 1534086495
EMCheckCompatibility: true
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
GraphicsCriticalError: |[0][GFX1]: Potential driver version mismatch ignored due to missing DLLs 0.0.0.0 and 0.0.0.0 (t=26.9531) 
InstallTime: 1492790905
Notes: FP(D000-L10010-W00000000-T0000) AdapterVendorID: 0x8086, AdapterDeviceID: 0x0162, AdapterSubsysID: 00000000, AdapterDriverVersion: 6.14.10.5398
D2D1.1? D2D1.1- D3D9 Layers? D3D9 Layers+ 
ProductID: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
ProductName: SeaMonkey
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 34973
StartupTime: 1534086448
SystemMemoryUsePercentage: 36
Theme: classic/1.0
Throttleable: 1
TotalPageFile: 7457308672
TotalPhysicalMemory: 3440480256
TotalVirtualMemory: 2147352576
URL: 
UptimeTS: 174.4410711
Vendor: Mozilla
Version: 2.46
Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 2 : 1 : 6 : 0x20066 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
 MSAFD Tcpip [UDP/IP] : 2 : 2 : 2 : 17 : 0x20609 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
 MSAFD Tcpip [RAW/IP] : 2 : 2 : 3 : 0 : 0x20609 : 0xc : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
 RSVP UDP Service Provider : 6 : 2 : 2 : 17 : 0x22609 : 0x8 : %SystemRoot%\system32\rsvpsp.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
 RSVP TCP Service Provider : 6 : 2 : 1 : 6 : 0x22066 : 0x8 : %SystemRoot%\system32\rsvpsp.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{1268D6E9-BAA1-4949-BBE9-23C63C9877E2}] SEQPACKET 0 : 2 : 17 : 5 : -2147483648 : 0x2000e : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{1268D6E9-BAA1-4949-BBE9-23C63C9877E2}] DATAGRAM 0 : 2 : 17 : 2 : -2147483648 : 0x20209 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{42FA7B62-7667-4713-A1D8-DF608F41DFE3}] SEQPACKET 1 : 2 : 17 : 5 : -1 : 0x2000e : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{42FA7B62-7667-4713-A1D8-DF608F41DFE3}] DATAGRAM 1 : 2 : 17 : 2 : -1 : 0x20209 : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{77AA4D22-EE55-471B-9D5A-E519CB7934F1}] SEQPACKET 2 : 2 : 17 : 5 : -2 : 0x2000e : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{77AA4D22-EE55-471B-9D5A-E519CB7934F1}] DATAGRAM 2 : 2 : 17 : 2 : -2 : 0x20209 : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{A9D3D48F-DA87-4669-821B-A10D668EFE4F}] SEQPACKET 3 : 2 : 17 : 5 : -3 : 0x2000e : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{A9D3D48F-DA87-4669-821B-A10D668EFE4F}] DATAGRAM 3 : 2 : 17 : 2 : -3 : 0x20209 : 0x0 : %SystemRoot%\system32\mswsock.dll :  : 8d5f1830-c273-11cf-95c8-00805f48a192
useragent_locale: en-US

This report also contains technical information about the state of the application when it crashed.
User avatar
James
Moderator
Posts: 27999
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Re: seamonkey crashing often with zonealarm 14

Post by James »

LMHmedchem
Posts: 78
Joined: August 31st, 2009, 2:29 pm

Re: seamonkey crashing often with zonealarm 14

Post by LMHmedchem »

James wrote:Crash reports is in about:crashes as they are then listed at https://crash-stats.mozilla.com/home/product/SeaMonkey'
https://support.mozilla.org/en-US/kb/mo ... shreporter
frg requested that I post a crash id, did I not post what was requested?

LMHmedchem
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: seamonkey crashing often with zonealarm 14

Post by frg »

james is right. You posted the crash but not the crash id which you can get from about:crashes or about:support.
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: seamonkey crashing often with zonealarm 14

Post by therube »

I see you have https everywhere in there.
Have you tried running SeaMonkey in Safe Mode?
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
LMHmedchem
Posts: 78
Joined: August 31st, 2009, 2:29 pm

Re: seamonkey crashing often with zonealarm 14

Post by LMHmedchem »

These are the crash id's that are currently listed in about:support,

Code: Select all

c7dbd9e7-7a2d-485b-8d4c-73bb8698cd9a   8/13/2018   4:54 PM
abfc937c-01de-4ad5-9dfd-36ca283769cb   8/13/2018   4:51 PM
aa121bdb-1b9b-4a10-8486-59b8a0e86224   8/13/2018   4:48 PM
54e74b13-dae4-4aae-bf66-ad7fcd92fd44   1/16/2018   1:12 PM
441fd8c4-5472-4198-8d3f-5f6cc6ea13ba   12/9/2017   12:07 AM
8b83fd47-92c2-48a1-ab85-15e4e6b93fe8   5/7/2017    1:19 PM
82e2c1bb-255a-4fb2-9ad1-4997e4667f41   3/30/2017   1:34 PM
69e56216-3ff6-4c05-9597-62fdbb6f65d4   8/13/2013   1:39 AM
33165fe9-36fc-43c1-8cae-4da535ff65e8   3/27/2013   8:16 PM
I have made some progress by adding rules to allow seamonkey to connect to local host (127.0.0.1), to the DNA server ip's, and to ports 80 and 443. At times when I start seamonkey, it cannot locate any servers. The zonealarm logs are so wretchedly useless that I had to install netmon so I might have some idea of what is happening when I can't make a connection or the program crashes. When I can't access any servers, it looks like the OS is trying to connect to DNS. There is name listed for the process trying to make the connection, so there is no way I can make a rule. After a while, I will get a popup from zone alarm that seamonkey is trying to access the internet. I allow and check to remember the rule, but this still keeps happening.

I have no idea why I don't immediately get a popup about something trying to make a connection that is blocked and I don't understand why the blocks keep happening even though I have checked remember the rule and have also added explicit rules to allow the connection anyway.

LMHmedchem
User avatar
James
Moderator
Posts: 27999
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Re: seamonkey crashing often with zonealarm 14

Post by James »

Since those crash reports do not have bp- at start they have not been submitted so click on them.
LMHmedchem
Posts: 78
Joined: August 31st, 2009, 2:29 pm

Re: seamonkey crashing often with zonealarm 14

Post by LMHmedchem »

James wrote:Since those crash reports do not have bp- at start they have not been submitted so click on them.
Clicking on the first report moves me to another page that looks like it is submitting a report. I get a message like "crash id found" and then seamonkey crashes again. After the crash, submitting the report with the normal crash reporter gives me a message that there was a problem submitting the report.

Again, there is no information whatsoever in the zone alarm logs indicating that something was blocked or anything useful. Seamonkey crash reporter has been checked off as trusted and allowed to connect to the internet zone, so I don't know what the issue would be.

When I tried to respond to this post, when I clicked submit, suddenly firefox couldn't find the server anymore. Looking at netmon, again there were multiple attempted connections to DNS with no process name. I think that zone alarm is blocking these connections for some reason but there is nothing in the logs to tell me one way or the other. If I quite firefox and restart, everything works, at least for a while. I am posting here using firefox since seamonkey is not stable enough. It took me 4 restarts of firefox to post this.

LMHmedchem
LMHmedchem
Posts: 78
Joined: August 31st, 2009, 2:29 pm

Re: seamonkey crashing often with zonealarm 14

Post by LMHmedchem »

Alright, I think I have managed to get the crash reports submitted. These are the numbers now.

Code: Select all

bp-dc8a40c6-e7fa-4e65-a6d4-af02e0180814  8/13/2018  8:56 PM
bp-a7c187fe-def0-4df9-a35e-11c9c0180814  8/13/2018  8:56 PM
bp-29c40c31-68dc-4edb-bd50-be0550180814  8/13/2018  4:51 PM
bp-08411f38-fe90-47fb-9f05-ea5ec0180814  8/13/2018  4:48 PM
LMHmedchem
User avatar
LIMPET235
Moderator
Posts: 39936
Joined: October 19th, 2007, 1:53 am
Location: The South Coast of N.S.W. Oz.

Re: seamonkey crashing often with zonealarm 14

Post by LIMPET235 »

Hi,
Just an idea here...seeing as you're having issues with ZA,,,
but how about you removing/un-installing Zone Alarm & using COMODO free firewall?
> https://www.comodo.com/home/internet-se ... covery.php

It does exactly what a good firewall should.
It's a tad "noisy" at first but then it just works.
[Ancient Amateur Astronomer.]
Win-10-H/64 bit/500G SSD/16 Gig Ram/450Watt PSU/350WattUPS/Firefox-115.0.2/T-bird-115.3.2./SnagIt-v10.0.1/MWP-7.12.125.

(Always choose the "Custom" Install.)
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: seamonkey crashing often with zonealarm 14

Post by frg »

At least the crash is not all over the place. The reference to the bug mentioned is not valid. Closed before 2.46

https://crash-stats.mozilla.com/report/ ... 0550180814

I would check the computer ram with memtest or another tool first. Might just be a coincidence.

Is this your processor?
https://ark.intel.com/products/68316/In ... o-3_60-GHz

If yes you are pushing it with XP. Make sure you use the latest available Intel chipset drivers for XP. Latest ones which had support were Westmere EP more or less i7 second generation I think. Sandy and Ivy bridge probably not officially.

FRG
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: seamonkey crashing often with zonealarm 14

Post by therube »

Can you still (manually) disable JIT (or running in Safe Mode should do it)?

And I suppose an OOM in JIT is different then a "regular" OOM issue (as in from eating more memory then one is safely able to consume on their end)?

Certainly removing ZA (& just using Windows Firewall itself) for a time while testing is in the cards, I would think.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Post Reply