AJAX Spider crashes Firefox

78 views
Skip to first unread message

Stephen McCants

unread,
May 17, 2017, 5:23:47 PM5/17/17
to OWASP ZAP User Group
Hello All,

OWASP ZAP 2.6.0
Firefox 53.0.2 (32-bit)

I'm able to successfully run Firefox configured to use the OWASP ZAP as a proxy and can see my page hits show up in the OWASP ZAP UI.  From the OWASP ZAP UI I can successfully run Active attacks and Spider attacks against my web application and all of this is using form based authentication successfully.  However, if I run the AJAX Spider it runs for a little while and then Firefox crashes without any error messages or error reports.  I get two identical dialogs concerning the crash (see screen shot "firefox_crash.png"):

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: firefox.exe
  Application Version: 53.0.2.6333
  Application Timestamp: 590bcebe
  Fault Module Name: xul.dll
  Fault Module Version: 53.0.2.6333
  Fault Module Timestamp: 590bd27e
  Exception Code: 80000003
  Exception Offset: 0089d467
  OS Version: 6.1.7601.2.1.0.274.10
  Locale ID: 1033
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


I looked in %AppData%\Roaming\Mozilla\Firefox\Crash Reports, but there was nothing about the crash there.  

I did find two messages about it in the Event Viewer:

- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-05-17T20:38:11.000000000Z" /> 
  <EventRecordID>97783</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>HCSDC3.hcs.us.com</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>firefox.exe</Data> 
  <Data>53.0.2.6333</Data> 
  <Data>590bcebe</Data> 
  <Data>xul.dll</Data> 
  <Data>53.0.2.6333</Data> 
  <Data>590bd27e</Data> 
  <Data>80000003</Data> 
  <Data>0089d467</Data> 
  <Data>1398</Data> 
  <Data>01d2cf4d79ff129b</Data> 
  <Data>C:\Program Files (x86)\Mozilla Firefox\firefox.exe</Data> 
  <Data>C:\Program Files (x86)\Mozilla Firefox\xul.dll</Data> 
  <Data>bd9a7e8c-3b40-11e7-8c77-080027ad0ca4</Data> 
  </EventData>
  </Event>

- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-05-17T20:38:11.000000000Z" /> 
  <EventRecordID>97782</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>HCSDC3.hcs.us.com</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>firefox.exe</Data> 
  <Data>53.0.2.6333</Data> 
  <Data>590bcebe</Data> 
  <Data>xul.dll</Data> 
  <Data>53.0.2.6333</Data> 
  <Data>590bd27e</Data> 
  <Data>80000003</Data> 
  <Data>0089d467</Data> 
  <Data>1300</Data> 
  <Data>01d2cf4d740b47a9</Data> 
  <Data>C:\Program Files (x86)\Mozilla Firefox\firefox.exe</Data> 
  <Data>C:\Program Files (x86)\Mozilla Firefox\xul.dll</Data> 
  <Data>bd7b7ffa-3b40-11e7-8c77-080027ad0ca4</Data> 
  </EventData>
  </Event>

Firefox has no add-ons or extensions.

Any ideas on why this might be crashing?

I'm going to try Chrome or something else in the mean time. 

Thanks!
--Stephen
firefox_crash.png

thc...@gmail.com

unread,
May 17, 2017, 7:08:16 PM5/17/17
to zaprox...@googlegroups.com
Hi.

That might have been fixed already (I recall some crash reports in the
geckodriver issue tracker).

I'm not sure if using latest Firefox (Nightly) and geckodriver (0.16.1)
would work (although that's the recommended), since we are still using
Selenium 2.x (one more reason to do the migration to Selenium 3).

Best regards.

Stephen McCants

unread,
May 17, 2017, 7:19:12 PM5/17/17
to OWASP ZAP User Group
Thanks for the suggestion.

I'm not using nightly builds of anything and would rather not if it can be helped.

I switched to Chrome and that seemed to work for me.
Reply all
Reply to author
Forward
0 new messages