Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox up to date but still crashing

  • 6 답장
  • 3 이 문제를 만남
  • 2 보기
  • 최종 답변자: philipp

more options

Here are my last few crash reports, please let me know if there is anything you need that can help solve this. Thanks in advance!

bp-b598db97-5360-498c-8300-d2b842161019 10/19/2016 6:36 PM 0a9839f3-e14b-4214-986b-8cac1809fb87 10/19/2016 5:12 PM 561fb51f-b963-4f4b-94dc-86617627d26e 10/19/2016 3:40 PM bp-d6b6d11b-9607-4763-a39d-f7ce02161003 10/3/2016 12:21 AM

Here are my last few crash reports, please let me know if there is anything you need that can help solve this. Thanks in advance! bp-b598db97-5360-498c-8300-d2b842161019 10/19/2016 6:36 PM 0a9839f3-e14b-4214-986b-8cac1809fb87 10/19/2016 5:12 PM 561fb51f-b963-4f4b-94dc-86617627d26e 10/19/2016 3:40 PM bp-d6b6d11b-9607-4763-a39d-f7ce02161003 10/3/2016 12:21 AM

모든 댓글 (6)

more options

Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

more options

bp-b598db97-5360-498c-8300-d2b842161019 bp-d6b6d11b-9607-4763-a39d-f7ce02161003

Signature: nsXPCWrappedJS::nsXPCWrappedJS

Total Virtual Memory 4,294,836,224 bytes (4 GB)

Available Virtual Memory 343,379,968 bytes (327.47 MB)

Available Page File 1,751,162,880 bytes (1.63 GB)

Available Physical Memory 369,537,024 bytes (352.42 MB)

System Memory Use Percentage 91

lpxpcom.dll = LastPass

inproc_agent.dll = Kaspersky Inproc Agent

This is for Sumo's Related Bugs 1295033 NEW --- Crash in nsXPCWrappedJS::nsXPCWrappedJS


Update/disable both LastPass and Kaspersky

more options

FredMcD said

bp-b598db97-5360-498c-8300-d2b842161019 bp-d6b6d11b-9607-4763-a39d-f7ce02161003 Signature: nsXPCWrappedJS::nsXPCWrappedJS Total Virtual Memory 4,294,836,224 bytes (4 GB) Available Virtual Memory 343,379,968 bytes (327.47 MB) Available Page File 1,751,162,880 bytes (1.63 GB) Available Physical Memory 369,537,024 bytes (352.42 MB) System Memory Use Percentage 91 lpxpcom.dll = LastPass inproc_agent.dll = Kaspersky Inproc Agent This is for Sumo's Related Bugs 1295033 NEW --- Crash in nsXPCWrappedJS::nsXPCWrappedJS

Update/disable both LastPass and Kaspersky


280e6180-4a81-439d-a94c-cf5ecc0a4b4f 10/22/2016 6:32 PM bp-e7ced4e9-02e8-4039-b9f2-d16c02161022 10/22/2016 6:30 PM bp-aee740e6-2864-4bb4-a018-d44602161021 10/21/2016 3:11 PM

Just crashed again but did not make it a report for some reason, I disabled both Lastpass and Kaspersky (I think) any other ideas?

more options

Is LastPass up-to-date on your machine?

more options

Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.


Signature: nsXPCWrappedJS::nsXPCWrappedJS

System Memory Use Percentage 91

lpxpcom.dll = LastPass

inproc_agent.dll = Kaspersky Inproc Agent

This is for Sumo's Related Bugs 1295033 NEW --- Crash in nsXPCWrappedJS::nsXPCWrappedJS


From bug report: Upgrading to Kaspersky 2017 (17.0.0.611) should fix the issue.


Remove LastPass and Kaspersky from your system. Any problem?

If not, get the current full installer of only one of them. Is there a problem?

more options

hi again Fire2Fox2, it might help debug the issue if we hand over the crash dump of your crashes over to kaspersky for further analysis. as a crash dump might contain private data (like the sites you were visiting at the time of the crash) we only do so with explicit consent of a user. would you be ok with that?