User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 Build ID: 20130107124423 Steps to reproduce: Nothing... had multiple windows and tiles open... for about 4 hours Actual results: Crashed without warning sp-processor06.phx1.mozilla.com_30576:2008; MDSW emitted no header lines; MDSW did not identify the crashing thread; CSignatureTool: No signature could be created because we do not know which thread crashed; MDSW emitted no frames; MDSW failed: 1; exploitablity tool: ERROR: could not process minidump; exploitablity tool failed: 1 Expected results: NA

Please provide the crash ID from about:crashes. Are you able to reproduce it consistently?

Per request: UUID 202db4bd-bfd4-478a-ac92-4423d2130122 Date Processed 2013-01-22 06:02:27 Uptime 50124 Last Crash 1.0 days before submission Install Age 1.0 days since version was first installed. Install Time 2013-01-21 05:12:31 Product Firefox Version 17.0.2esr Build ID 20130107124423 Release Channel esr Have not been able to re-create consistently.... but NOTE: I had to downgrade from FF 18.0.1 which WAS crashing consistently upon a) closing a separate FF window b) close a Tab withing a set of Tabs in a FF window c) just sudden w/no reason I did try running in SAFE MODE, but problem continued. this started on the 1/19 after upgrade to 18.0.1 and rebooting my PC... here are the CrashIDs: bp-10575b1d-4329-42cc-ba07-0cbd021301221/21/20133:00 AM 78dffea8-44b9-4a50-bad8-7a45bec91d9a1/21/201312:28 AM bp-29a3ad81-cbb8-4705-9c79-3779e21301211/20/20139:10 PM bp-8bf7e5bd-52bf-4562-bf08-5c4a021301211/20/20139:09 PM bp-f5baa6bd-eb00-4173-aa2e-e1f2f21301211/20/20139:06 PM bp-96c89713-3296-455e-8dde-5d4a921301211/20/20139:04 PM bp-d1fa1bba-bf72-47b2-b352-f258e21301211/20/20139:01 PM bp-36618ec8-dc47-4d03-9a91-27d6521301211/20/20139:00 PM bp-db0981eb-d71e-4645-bf9c-ba61721301211/20/20138:57 PM bp-b5bd6641-c920-4221-b644-dea9a21301211/20/20135:14 PM bp-ef16d962-d4a9-440b-b4ba-0cb2821301211/20/20135:06 PM bp-c6cebb49-7996-42db-82d0-ae23f21301211/20/20135:01 PM bp-9a37dd97-d7be-48a3-b60f-7546921301211/20/20134:44 bp-41b46ae3-9435-4948-8a46-7a92921301211/20/20134:26 PM bp-ef88fdf6-7a41-412c-87f9-7b2d521301201/20/20137:07 AM bp-b2cad709-2d14-4a6a-967b-7ca2021301201/20/201312:17 AM bp-3bdebcfc-485f-4dbc-8d49-68d4321301201/20/201312:09 AM bp-48abfc8e-de60-4680-a8a1-cfb5e21301201/19/201311:10 PM bp-315ba21c-a994-4bdc-86e4-5a1ae21301201/19/201310:54 PM bp-02842472-3500-4614-bfa1-a373621301201/19/201310:24 PM bp-aa728f1e-6061-4195-abd1-c1e8021301201/19/201310:20 PM bp-c06f77dc-29aa-4ebe-aa3b-6a70921301201/19/201310:05 PM bp-21b4aa48-574c-40a8-9427-ba11221301201/19/20137:46 PM bp-dac9ab16-ee22-4595-807c-d9e8921301201/19/20137:36 PM bp-2e4f438a-3d2b-4f10-958b-42e6a21301201/19/20137:35 PM bp-be627b43-a4a0-4893-b21f-1b31421301201/19/20137:35 PM 5a4d1a30-f3e9-488a-9029-d5be4877c5951/19/201312:18 AM

The empty crash signature means Mozilla doesn't know where Firefox crashed so steps to reproduce are required. In your case, you hit bug 803808 in 17.0.2esr and bug 783369 in 18.0.1 (caused by Norton). I assume they are the same.

(In reply to Scoobidiver from comment #3) > bug 803808 I meant bug 830808.