New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 29 users

Issue metadata

Status: Verified
Not on Chrome anymore
Closed: Oct 2011
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

  • Only users with EditIssue permission may comment.

Sign in to add a comment

Issue 97319: Netflix returns with Silverlight Application Storage Error (N8010) when "Clear cookies and other site and plug-in data when I close my browser" is selected

Reported by, Sep 20 2011 Project Member

Issue description

Chrome Version       : 14.0.835.186 m, 16.0.887.0 canary
OS                   : Windows 7 enterprise

We are seeing a number of users report in the Chrome help forum that they are not able to Instant Play movies/shows.  Instead they get "Silverlight Application Storage Error (N8010)". See screenshot.

What steps will reproduce the problem?
1. In options, select "Clear cookies and other site data when I close my browser"
2. Exit and restart Chrome
3. Log into Netflix
4. Instant play

What is the expected result?
Expect movie/show to play

What happens instead?
Receive Silverlight Application Storage Error (N8010).  See screenshot.

Note: If the option "Clear cookies and other site data when I close my browser" is de-selected after seeing the error, refreshing the Netflix error page will cause the movie to play again.  No browser restart needed.
Netflix N8010.JPG
47.7 KB View Download

Comment 2 by, Sep 21 2011


Comment 3 by, Sep 22 2011


Comment 4 by, Sep 22 2011


Comment 5 by, Sep 26 2011

 Issue 97169  has been merged into this issue.

Comment 6 Deleted

Comment 7 Deleted

Comment 8 by, Sep 30 2011

Status: Assigned

Comment 9 by, Oct 3 2011

Unchecking the "Clear cookies on exit" box solved the problem for me too.  I rechecked the box while the movie was playing and a Silverlight popup came up to complain about protected content, but the movie did keep playing.

Comment 10 by, Oct 4 2011

It appears this was an "intentional" change:

With this change, apparently "NPNVprivateModeBool" will be set to true if site data is to be cleared on exit. I can see why this is considered desirable (we want to ensure that the plugin does not leave data on disk) but I don't know if it will be possible for a plugin like Netflix (which presumably really wants to cache some video data on disk) to operate under this mode. It would have to offer a strong guarantee that its cache would be cleared at shutdown.

Comment 11 by, Oct 4 2011

Seems like we should probably reach out to Netflix to have them update their error message.

> It would have to offer a strong guarantee that its cache would be cleared at shutdown.

The problem is that shutdown in terms of that pref is *profile* shutdown, and plugin instances aren't per-profile (nor do plugins understand the concept of a profile). So there's no way a plugin could do the right thing here, which is presumably why we changed this.

On the other hand, it's really unfortunate that so soon after getting an NPAPI spec for clearing data at the browser's request, we made it useless via multi-profile.

(Also, don't plugins generally already not distinguish between browsers in storing local state? If so, why do we enforce a stronger correctness requirement on the behavior of multi-profile than we do on multi-browser?)

Comment 12 by, Oct 4 2011

So mirandac and I just talked about this, and we think the right change is actually to not do this, and to have browser shutdown clear plugin state if any profile active during the session had this pref set when it was destroyed.

It's not perfect, but it seems better than the current approach (and arguably better than doing the clearing as the profile is destroyed, even if people using multiple browsers already could have issues with state being destroyed--certainly it's safer, so it's the best fix for stable, and we could experiment with doing the other approach on dev if we want to).

erikwright or bauerb, could one of you make that change?

Comment 13 by, Oct 4 2011

This bug is in stable, though I don't know how many users are affected or how problematic it is for them to turn off this option.

The proposed solution sounds like it might exceed what is reasonable for a stable merge.

kareng, can you comment on whether you think a stable fix is needed?

I have to admit that I know very little (i.e. nothing) about NPAPI so I don't think I'm a good candidate to implement this. Especially not if it's supposed to happen quickly to try to reach stable.

Comment 14 by, Oct 5 2011

Comment 9 helped solve this problem.

Comment 15 by, Oct 5 2011

Comment 9 did not work for me, nor did clearing all cookies etc. It also will not work in Firefox... I get the same "private browsing" message but with slightly different wording. On the other hand, using the same account, my friend is able to stream, on MY account, with a different (still Windows) computer.

Comment 16 by, Oct 5 2011

I talked to Erik about it, and I think ;) that for a fix on stable we should simply not pass the private mode flag to Silverlight (when "clear site data on exit" is checked, that is. We should still do it in incognito mode). AFAIK Silverlight never implemented the ClearSiteData API, so we're not regressing anything here, and that would be a much smaller change then reverting 91168 or implementing the behavior Stuart suggested.

Comment 17 by, Oct 5 2011

Comment 15 is interesting to me. A friend was able to stream on my account as well - using a Windows laptop at a different location. I believe that machine runs Windows 7. I run XP.
Comment 9 does work for me, although I have not tried rechecking the box during play.

Netflix works in my Firefox in that I do not get the error notice discussed here; however, if I go to full screen view with it, the video freezes.

Comment 18 by, Oct 6 2011

> for a fix on stable we should simply not pass the private mode flag to Silverlight
> (when "clear site data on exit" is checked

Agreed, that's definitely a much safer fix for stable.

Comment 19 by, Oct 6 2011

Actually, a better version of that would be "only pass the flag to Flash" in that case, since we are currently plugin-limiting the clearing to Flash anyway (

Comment 20 by, Oct 6 2011

Yes, that's what I meant.

Comment 21 by, Oct 6 2011

Per discussion bauerb and mirandac, we're doing comment 16/19, and holding off on the more extensive fix until some larger discussion of that pref has been resolved. If necessary, we'll do 12 down the road, but we hope it won't be due to bigger changes to what the pref means.

-> bauerb, who has graciously agreed to fix it.

Comment 22 by, Oct 6 2011

Status: Started
OK, (for the fix on stable) is up. Would someone mind patching it in and trying out whether Netflix works with it? I don't have a Netflix account.

Comment 23 by, Oct 6 2011

I have an account and can help test when it's patched.

Comment 24 Deleted

Comment 25 by, Oct 7 2011

My problem was solved: 

I called them up--long story short, you have to clear your silverlight cache. To do so, I went to 


And then you delete the "is" folder. From what the netflix lady told me, that's Silverlight's cache--and if anything corrupted gets in there, or something, if you clear it out, you'll be set! 

Now my computer works with Netflix. If that doesn't work, then, it may be a network problem.

Comment 26 by, Oct 7 2011

Comment 25 did not work for me. I did that once over the phone with Netflix and once on my own later. It did not help at all.

Comment 27 by, Oct 10 2011

Labels: Merge-Requested Mstone-15
Bugdroid seems not to have picked it up, but landed in http://crrev.com104507. Can we merge this to M15 or do we want to let it bake for a bit more?

Comment 28 by, Oct 10 2011

Labels: -Merge-Requested Merge-Approved

Comment 29 by, Oct 10 2011

Status: Fixed
I just tested it on Canary (16.0.904.0 canary), and was able to play a movie (instant play) with "Clear cookies and other site data when I close my browser" selected. Confirmed fixed.

Comment 30 by, Oct 12 2011

Status: Verified
verified as working on 15.0.874.92 on Win7 64 bit

Comment 31 by, Oct 17 2011

Labels: -Merge-Approved Merge-Merged

Comment 32 by, Oct 26 2011

Reproducible on Chrome OS 0.15.1011.104 (Chrome 15.0.874.104) - Mario

Comment 33 by, Oct 28 2011

The issue appears to have been resolved with the latest update.

Comment 34 Deleted

Comment 35 by, Oct 13 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 36 by, Mar 10 2013

Project Member
Labels: -Area-UI -Feature-Plugins -Mstone-15 Cr-UI Cr-Content-Plugins M-15

Comment 37 by, Mar 13 2013

Project Member
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Comment 38 by, Apr 6 2013

Project Member
Labels: Cr-Blink

Comment 39 by, Apr 6 2013

Project Member
Labels: -Cr-Content-Plugins Cr-Internals-Plugins

Sign in to add a comment