Skip to content

Loading…

`Error: Attempting to use a disconnected port object` #383

Closed
gorhill opened this Issue · 0 comments

1 participant

@gorhill

Repro steps:

  • Go to "3rd-party filters"
  • Force a reload of filter lists (however you wish)
  • Quickly change dashboard tab before the reload of the filter lists complete

Error message in console of extension:

Error in response to storage.get: Error: Attempting to use a disconnected port object
    at callback (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/vapi-background.js:253:18)
    at onMetadataReady (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/messaging.js:483:9)
    at checkCacheObsolescence (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:934:9)
    at onRepoMetaReady (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:954:9)
    at µBlock.assets.getRepoMetadata (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:287:13)
    at onCacheMetaReady (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:977:9)
    at Object.µBlock.assets.getEntries [as entries] (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:96:13)
    at onBuiltinListsLoaded (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/storage.js:223:22)
    at reportBack (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:663:9)
    at XMLHttpRequest.onInstallFileLoaded (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:669:9)
    at XMLHttpRequest.onResponseReceived (chrome-extension://lgbmdnkabkjpmegohhnoabimkbfapigk/js/assets.js:240:27)

Maybe adding a disconnected property on the port object could work, this way the closure approach could still be used.

I suppose using a slower computer help makes this problem more easy to reproduce.

@gorhill gorhill added a commit that closed this issue
@gorhill gorhill code review, fixes #383 a087190
@gorhill gorhill closed this in a087190
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.