Mozilla 도움말 검색

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

자세히 살펴보기

bad script XDR magic number

  • 1 답장
  • 15 이 문제를 만남
  • 4 보기
  • 최종 답변자: Andrew

more options

When opening an asp.net application, i find this in the error console.

Timestamp: 3/7/2013 10:12:56 PM Error: bad script XDR magic number

What does this error mean ?

Also sometimes we get the following errors..

Timestamp: 3/7/2013 8:00:22 AM Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.sessionHistory]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml ::  :: line 716" data: no] Source File: chrome://global/content/bindings/browser.xml Line: 723

Timestamp: 3/7/2013 8:00:22 AM Error: this.docShell is null Source File: chrome://global/content/bindings/browser.xml Line: 323

Timestamp: 3/7/2013 8:00:22 AM Error: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628. Source File: chrome://browser/content/tabbrowser.xml

When opening an asp.net application, i find this in the error console. Timestamp: 3/7/2013 10:12:56 PM Error: bad script XDR magic number What does this error mean ? Also sometimes we get the following errors.. Timestamp: 3/7/2013 8:00:22 AM Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.sessionHistory]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: :: line 716" data: no] Source File: chrome://global/content/bindings/browser.xml Line: 723 Timestamp: 3/7/2013 8:00:22 AM Error: this.docShell is null Source File: chrome://global/content/bindings/browser.xml Line: 323 Timestamp: 3/7/2013 8:00:22 AM Error: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628. Source File: chrome://browser/content/tabbrowser.xml

모든 댓글 (1)

more options

Hello!

Thanks for reaching out to Mozilla Support about your issue. We value and appreciate you as a user.

Please update to version 19.0.2 to fix see if the issue is fixed.

Best Regards,

feer56


Did you know that Mozilla Support is helped out by volunteers? Be part of SUMO! http://mzl.la/OJtpch


If any response posted satisfies you to be your solution, please mark it as your solution.