Closed Bug 765497 Opened 13 years ago Closed 13 years ago

Error: SecurityError: The operation is insecure. in skydrive.live.com

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Version:
13 Branch
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 762409
Tracking Flags:
Tracking Status
firefox13 - ---

People

(Reporter: alice0775, Assigned: mayhemer)

References

Details

(Keywords: regression)

Build Identifier: http://hg.mozilla.org/mozilla-central/rev/4e3362864fbd Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0a1 ID:20120616030538 When I test Bug 763593 and, Bug 765494. Error: SecurityError: The operation is insecure. in skydrive.live.com Steps to Reproduce: 1. Open Error Console 2. Open https://skydrive.live.com/?cid=654125A09BEBAF67&id=654125A09BEBAF67!245 Actual Results: Error: SecurityError: The operation is insecure. Source file: https://secure.wlxrs.com/rgPTk2qGTSSYyPdUalCQWA/wlive.js Line: 1 Expected Results: No error Regression window(m-c) Last Good: http://hg.mozilla.org/mozilla-central/rev/6881fa89cfca Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120404 Firefox/14.0a1 ID:20120404001322 First Bad: http://hg.mozilla.org/mozilla-central/rev/638769f8ec54 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120404 Firefox/14.0a1 ID:20120404043722 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6881fa89cfca&tochange=638769f8ec54 Regression window(m-i) Last Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/01c41b9cd650 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120403 Firefox/14.0a1 ID:20120403165122 First Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/308440acc7b7 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120403 Firefox/14.0a1 ID:20120403172325 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=01c41b9cd650&tochange=308440acc7b7
I saw the following error message in Error Console even with "good" builds (including Firefox 13). -- uncaught exception: [Exception... "The operation is insecure." code: "18" nsresult: "0x80530012 (SecurityError)" location: "https://secure.wlxrs.com/rgPTk2qGTSSYyPdUalCQWA/wlive.js Line: 1"] -- Bug 739659 just changed the error message.
OK Regression window(m-c) Good: http://hg.mozilla.org/mozilla-central/rev/6fe899b9b372 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120223 Firefox/13.0a1 ID:20120223152933 Bad: http://hg.mozilla.org/mozilla-central/rev/d23600a1d4a7 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120223 Firefox/13.0a1 ID:20120223183629 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6fe899b9b372&tochange=d23600a1d4a7 Regression window(m-i) Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/0987e5b0d371 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120223 Firefox/13.0a1 ID:20120223081529 Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/1b1c461e3ba0 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120223 Firefox/13.0a1 ID:20120223094930 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0987e5b0d371&tochange=1b1c461e3ba0 Triggered by:Bug 495337
Blocks: 495337
Version: 14 Branch → 13 Branch
Status: UNCONFIRMED → NEW
tracking-firefox13: --- → ?
tracking-firefox14: --- → ?
tracking-firefox15: --- → ?
tracking-firefox16: --- → ?
Ever confirmed: true
Keywords: regression
Assignee: nobody → honzab.moz
tracking-firefox13: ? → -
tracking-firefox14: ? → +
tracking-firefox15: ? → +
tracking-firefox16: ? → +
I believe this is dup of bug 762409. I cannot reproduce this particular bug with current m-c and putting condition breakpoint on |subsumes| at [1] I can see the patch gets executed. [1] http://hg.mozilla.org/mozilla-central/annotate/d29af708ec3c/dom/src/storage/nsDOMStorage.cpp#l1714
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
untracking the dupe bug.
tracking-firefox14: + → ---
tracking-firefox15: + → ---
tracking-firefox16: + → ---
You need to log in before you can comment on or make changes to this bug.