Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 25 replies
  • Subscribers 1 subscriber
  • Views 30707 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Crash - Chrome

minimoo
Hello,
Just wondering if anyone else is aware of the sophos web intelligence module seemingly crashing within google chrome:
 
Faulting application name: chrome.exe, version: 0.0.0.0, time stamp: 0x4d490687
Faulting module name: swi_filter_0001.dll, version: 1.0.5.0, time stamp: 0x4ca1f9cb
Exception code: 0xc0000005
Fault offset: 0x00014915
Faulting process id: 0x1920
Faulting application start time: 0x01cbc55d3a55a1c0
Faulting application path: C:\Users\Paul\AppData\Local\Google\Chrome\Application\chrome.exe
Faulting module path: C:\Program Files (x86)\Sophos\Sophos Anti-Virus\Web Intelligence\swi_filter_0001.dll
Report Id: 5d749190-3153-11e0-9750-001a92782b5b

Faulting application name: chrome.exe, version: 0.0.0.0, time stamp: 0x4d490687

Faulting module name: swi_filter_0001.dll, version: 1.0.5.0, time stamp: 0x4ca1f9cbException code: 0xc0000005

Fault offset: 0x00014915

Faulting process id: 0x1920

Faulting application start time: 0x01cbc55d3a55a1c0

Faulting application path: C:\Users\Paul\AppData\Local\Google\Chrome\Application\chrome.exe

Faulting module path: C:\Program Files (x86)\Sophos\Sophos Anti-Virus\Web Intelligence\swi_filter_0001.dll

Report Id: 5d749190-3153-11e0-9750-001a92782b5b

FAULTING_IP: 

swi_filter_0001!HTTPFilterBlockPageBytesProcessed+124e5

70084915 8a1a            mov     bl,byte ptr [edx]

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)

ExceptionAddress: 70084915 (swi_filter_0001!HTTPFilterBlockPageBytesProcessed+0x000124e5)

   ExceptionCode: c0000005 (Access violation)

  ExceptionFlags: 00000000

NumberParameters: 2

   Parameter[0]: 00000000

   Parameter[1]: 068f5000

Attempt to read from address 068f5000

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
044ff5fc 700846fe 0632cff8 068f5000 ffffffff swi_filter_0001!HTTPFilterBlockPageBytesProcessed+0x124e5
044ff618 7008484d ffffffff 0632ced0 7007fa73 swi_filter_0001!HTTPFilterBlockPageBytesProcessed+0x122ce
044ff624 7007fa73 0632ce60 044ff710 0632c580 swi_filter_0001!HTTPFilterBlockPageBytesProcessed+0x1241d
044ff634 70077ac4 068f3224 ffffffff 870d0489 swi_filter_0001!HTTPFilterBlockPageBytesProcessed+0xd643
044ff688 778f8a18 02d80000 00d80ca0 00000000 swi_filter_0001!HTTPFilterBlockPageBytesProcessed+0x5694
044ff6c8 02d80ad0 044ff7c0 778f2e5e 02d80138 ntdll!RtlpDeCommitFreeBlock+0x9a
044ff710 70071f0c 068f3000 870d0519 00000000 0x2d80ad0
044ff7d8 72611fc2 0632c580 068f3000 00000223 swi_filter_0001!HTTPFilterRecvFromServer+0x4c
00000000 00000000 00000000 00000000 00000000 swi_lsp+0x1fc2
:8837


This thread was automatically locked due to age.
Parents
  • 0

    Hi Alex,

    As Jak says, a support ticket is the best way to get our attention e.g. issues will get escalated to the dev team. Some things that are quite useful for us to know (and the support team will ask):

    1. is it something specific to a particular site?

    2. is it something that affects a particular browser?

    3. a fiddler trace or wireshark or similar is really useful (having traces with and without our code running is beneficial)

    4. an SDU can be really useful, but we'll at least need to know what version you have installed

    5. crash dumps are extremely useful (when we can pinpoint the defective code quickly, we can usually fix it in an upcoming maintenance release)

    By the way, network traces may contain sensitive information. Be sure to review it (and remove any confidential information) before submitting files to the support team.

    Thanks,

    Bob Cook

    Development Manager, Sophos Vancouver

    (I'm responsible for the web filtering components in the Sophos endpoint products)

    :22251
Reply
  • 0

    Hi Alex,

    As Jak says, a support ticket is the best way to get our attention e.g. issues will get escalated to the dev team. Some things that are quite useful for us to know (and the support team will ask):

    1. is it something specific to a particular site?

    2. is it something that affects a particular browser?

    3. a fiddler trace or wireshark or similar is really useful (having traces with and without our code running is beneficial)

    4. an SDU can be really useful, but we'll at least need to know what version you have installed

    5. crash dumps are extremely useful (when we can pinpoint the defective code quickly, we can usually fix it in an upcoming maintenance release)

    By the way, network traces may contain sensitive information. Be sure to review it (and remove any confidential information) before submitting files to the support team.

    Thanks,

    Bob Cook

    Development Manager, Sophos Vancouver

    (I'm responsible for the web filtering components in the Sophos endpoint products)

    :22251
Children
No Data