An error occurred in Firefox Profiler

[gmalafskyCRD]

[Exception... "File error: Is locked" nsresult: "0x8052000e (NS_ERROR_FILE_IS_LOCKED)" location: "JS frame :: https://profiler.firefox.com/main.4a777f3d5ed181a655f4.bundle.js :: _getPersistedLocale :: line 147" data: no].

┆Issue is synchronized with this Jira Task

[julienw]

Thanks for your report. We need some more information, especially your steps to reproduce, but also where you saw this error message, your environment. Thanks

[gmalafskyCRD]

I was trying to profile wsj.com which is not loading completely and is taking extremely long time for what it is loading. This just started today. I do not have a problem loading it with MS Edge. In Console view, the page apparently has a large number of errors. Which I attached. Since many of these have file locked errors, I suspect it is same root cause as preventing profiler from working. I haven’t been able to get further than this though in figuring out problem. Other web sites aren’t as bad but still not good such as Walmart.com. I attached its Console as well which shows many errors.

I have VUE DEV TOOL installed as well as Dark Reader, EPUBReader, uBlock (turned off for wsj).

FYI:

This is likely not your area but in case it is worthwhile to you--

I have been using FF as my main browser both for general web and also for client side code development. Note I just spent 2 days figuring out why debugger was not working with VUE page script after doing so fine for a long time. Turned out to be problem with Chrome as well, as sporadically with Edge but not always there. Finally got resolved with webpack black art using vue-source-loader add-on, and forcing webpack to make file source maps using BUILD instead of SERVE. In this case, seems although webpack correctly had its source map information made, browsers were not getting the maps to the JS within the vue pages although standalone JS files worked fine.

From: Julien Wajsberg @.> Sent: Thursday, April 20, 2023 9:34 AM To: firefox-devtools/profiler @.> Cc: gmalafskyCRD @.>; Author @.> Subject: Re: [firefox-devtools/profiler] An error occurred in Firefox Profiler (Issue #4583)

Thanks for your report. We need some more information, especially your steps to reproduce, but also where you saw this error message, your environment. Thanks

— Reply to this email directly, view it on GitHub https://github.com/firefox-devtools/profiler/issues/4583#issuecomment-1516441433 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A27CR7GVX444GCDC3CEZ2G3XCFCNPANCNFSM6AAAAAAXFRWNXU . You are receiving this because you authored the thread.Message ID: @.***>

Content-Security-Policy warnings 45 Some cookies are misusing the recommended “SameSite“ attribute 23 Cookie “AID” has been rejected because it is already expired. www.walmart.com Cookie “xptc” has been rejected because it is already expired. www.walmart.com Cookie “bm_mi” has been rejected because it is already expired. www.walmart.com EvalError: call to eval() blocked by CSP hook.js:1:48209 Content Security Policy: The page’s settings blocked the loading of a resource at eval (“script-src”). Source: ;(function r(e,t=!1){const o="6.0";let i… www.walmart.com Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). www.walmart.com:1:1 Content Security Policy: The page’s settings blocked the loading of a resource at https://www.walmart.com/akam/13/1706e14a (“script-src”). www.walmart.com Loading failed for the Githubissues.

Githubissues is a development platform for aggregating issues.