`react-doctor/no-create-object-url-without-revoke`

createObjectURL without revokeObjectURL

Category: Performance
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: always
Tags: test-noise
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-create-object-url-without-revoke. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

const download = (blob) => {
  link.href = URL.createObjectURL(blob);
  link.click();
};

Corrected pattern

const download = (blob) => {
  const objectUrl = URL.createObjectURL(blob);
  try {
    link.href = objectUrl;
    link.click();
  } finally {
    URL.revokeObjectURL(objectUrl);
  }
};

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/no-create-object-url-without-revoke diagnostic in the current repository. Required change: - Call URL.revokeObjectURL(url) once the object URL is no longer needed (after the download, in a useEffect cleanup, or on unmount). An object URL keeps its Blob/File alive for the document lifetime until it is revoked.

Reference transformation:Before:

const download = (blob) => {
  link.href = URL.createObjectURL(blob);
  link.click();
};

After:

const download = (blob) => {
  const objectUrl = URL.createObjectURL(blob);
  try {
    link.href = objectUrl;
    link.click();
  } finally {
    URL.revokeObjectURL(objectUrl);
  }
};

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Preserve resource ownership and cleanup. Do not move work into a hotter render or frame path. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Performance rules from the rules reference:

react-doctor/no-document-write: document.write/writeln
react-doctor/no-dynamic-import-path: Use a string-literal path: `import('./feature/heavy.js')` so the bundler can split this chunk
react-doctor/no-eager-new-in-use-state-initializer: Eager constructor in useState initializer
react-doctor/no-ease-in-motion: UI motion starts with ease-in
react-doctor/no-excessive-motion-stagger: Motion child stagger is too long

react-doctor/no-create-object-url-without-revoke