"Property storage exceeds 196607 properties" error when using `fetch` more than a certain number of times in React Native #39441

ishikawa · 2023-09-14T10:16:52Z

Description

We are developing an application using React Native and Expo. This application needs to run 24/7 and performs network requests using fetch() regularly for monitoring purposes.

The issue we are facing is that after running the application for a while, from some point, network requests starting to fail. Through investigation using logs from Sentry, we have identified the following problem:

We are using fetch() for network requests.
At the completion of a fetch() request, an error occurs: Property storage exceeds 196607 properties.

The stack trace when this error occurs is as follows:

message: Property storage exceeds 196607 properties,
name: RangeError,
stack:
RangeError: Property storage exceeds 196607 properties
    at register (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:13781:20)
    at createFromOptions (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:13614:30)
    at get (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:13182:67)
    at anonymous (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:15155:45)
    at call (native)
    at dispatchEvent (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:14686:31)
    at setReadyState (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:13481:31)
    at __didCompleteResponse (/Users/expo/Library/Developer/Xcode/DerivedData/xxx/main.jsbundle:13289:29)
    at apply (native)
    at anonymous

Through further investigation, the following findings have been uncovered:

The polyfill used for fetch, whatwg-fetch, returns responses as Blob objects.
When a Blob is created, it is registered with blobID in the BlobRegistry, which is not automatically released.
This issue was previously reported in fetch() leaks memory on each request due to unreleased Blobs #19248 and was fixed by modifying whatwg-fetch. However, with the implementation of automatic garbage collection in [Blob] Release underlying resources when JS instance in GC'ed on iOS #24405, the implementation was reverted in commit bccc92d, returning to the original behavior.
Although [Blob] Release underlying resources when JS instance in GC'ed on iOS #24405 enables Blob objects to be garbage collected, the Blob IDs registered in the BlobRegistry remain, causing the count to increase each time fetch is called.
As a result, the Property storage exceeds 196607 properties error occurs

Our solution

To address this issue and prevent the error, we have modified the implementation of BlobRegistry to use a Map instead of an object. By using a Map, there is no limit to the number of entries.

const registry: Map<String, number> = new Map();

const register = (id: string) => {
  const used = registry.get(id);

  if (used != null) {
    registry.set(id, used + 1);
  } else {
    registry.set(id, 1);
  }
};

const unregister = (id: string) => {
  const used = registry.get(id);

  if (used != null) {
    if (used <= 1) {
      registry.delete(id);
    } else {
      registry.set(id, used - 1);
    }
  }
};

const has = (id: string): number | boolean => {
  return registry.get(id) || false;
};

module.exports = {
  register,
  unregister,
  has,
};

React Native Version

0.72.4

Output of `npx react-native info`

System:
OS: macOS 13.4.1
CPU: (8) arm64 Apple M2
Memory: 92.86 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 18.17.0
path: /usr/local/bin/node
Yarn:
version: 1.22.19
path: /usr/local/bin/yarn
npm:
version: 9.6.7
path: /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.12.1
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8815526
Xcode:
version: 14.3/14E222b
path: /usr/bin/xcodebuild
Languages:
Java: Not Found
Ruby:
version: 3.2.2
path: /Users/takanori.ishikawa/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.4
wanted: 0.72.4
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found

Steps to reproduce

Invoke fetch() more than 196,607 times 😄

Snack, screenshot, or link to a repository

To demonstrate this issue, I created a simple Expo application.
https://github.com/ishikawa/react-native-fetch-property-storage-exceeds-error

You can run it with expo:

$ npm i
$ npm run ios

The text was updated successfully, but these errors were encountered:

ishikawa · 2023-09-19T09:24:12Z

I also added PR #39528

Summary: issue: #39441 For the following reasons, I have replaced an object used for id management inside BlobRegistry with `Map`. - The polyfill used for `fetch`, [whatwg-fetch](https://github.com/JakeChampion/fetch), returns responses as `Blob` objects. - When a `Blob` is created, it is registered with blobID in the [BlobRegistry](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Blob/BlobRegistry.js), which is not automatically released. - This issue was previously reported in #19248 and was fixed by modifying whatwg-fetch. However, with the implementation of automatic garbage collection in #24405, the implementation was reverted in commit bccc92d, returning to the original behavior. - Although #24405 enables `Blob` objects to be garbage collected, the Blob IDs registered in the BlobRegistry remain, causing the count to increase each time `fetch` is called. - As a result, the `Property storage exceeds 196607 properties` error occurs To address this issue, I have modified the implementation of `BlobRegistry` to use a `Map` instead of an object. By using a `Map`, there is no limit to the number of entries. ## Changelog: [Internal] - [Fixed] - Fixed a bug that caused a "Property storage exceeds 196607 properties" error when sending a certain number of `fetch` requests. Pull Request resolved: #39528 Test Plan: I've added a new tests in `packages/react-native/Libraries/Blob/__tests__/BlobRegistry-test.js` and confirmed the test pass before and after changes. ``` $ yarn run test ... Test Suites: 1 skipped, 219 passed, 219 of 220 total Tests: 2 skipped, 4017 passed, 4019 total Snapshots: 1154 passed, 1154 total Time: 10.525 s Ran all test suites. ✨ Done in 12.52s. ``` Reviewed By: javache Differential Revision: D49423213 Pulled By: NickGerleman fbshipit-source-id: d5f73d7f5e34d1d2c3969b7dfbc45d3e6196aa30

ishikawa · 2023-09-20T23:15:40Z

The fix is merged #39528 in deca8c5. Thanks!

Summary: issue: facebook#39441 For the following reasons, I have replaced an object used for id management inside BlobRegistry with `Map`. - The polyfill used for `fetch`, [whatwg-fetch](https://github.com/JakeChampion/fetch), returns responses as `Blob` objects. - When a `Blob` is created, it is registered with blobID in the [BlobRegistry](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Blob/BlobRegistry.js), which is not automatically released. - This issue was previously reported in facebook#19248 and was fixed by modifying whatwg-fetch. However, with the implementation of automatic garbage collection in facebook#24405, the implementation was reverted in commit bccc92d, returning to the original behavior. - Although facebook#24405 enables `Blob` objects to be garbage collected, the Blob IDs registered in the BlobRegistry remain, causing the count to increase each time `fetch` is called. - As a result, the `Property storage exceeds 196607 properties` error occurs To address this issue, I have modified the implementation of `BlobRegistry` to use a `Map` instead of an object. By using a `Map`, there is no limit to the number of entries. ## Changelog: [Internal] - [Fixed] - Fixed a bug that caused a "Property storage exceeds 196607 properties" error when sending a certain number of `fetch` requests. Pull Request resolved: facebook#39528 Test Plan: I've added a new tests in `packages/react-native/Libraries/Blob/__tests__/BlobRegistry-test.js` and confirmed the test pass before and after changes. ``` $ yarn run test ... Test Suites: 1 skipped, 219 passed, 219 of 220 total Tests: 2 skipped, 4017 passed, 4019 total Snapshots: 1154 passed, 1154 total Time: 10.525 s Ran all test suites. ✨ Done in 12.52s. ``` Reviewed By: javache Differential Revision: D49423213 Pulled By: NickGerleman fbshipit-source-id: d5f73d7f5e34d1d2c3969b7dfbc45d3e6196aa30

robsadams · 2023-09-29T17:00:10Z

Will this be in release 0.72.4 and beyond? ... I have the same issue.

Ladvace · 2023-12-24T16:00:01Z

getting same issue too

robsadams · 2024-01-05T17:53:38Z

Is this rolled back to react-native .71.2? If so, does anybody know how to pick it up on vscode? I am already using react-native tools which seems to be using react-native .71.2.... I can't find instructions to pick up patches or upgrade react native within vscode.

brunomartins-com · 2024-01-13T21:39:33Z

Do you guys know which version it is fixed? I am using 0.72.6 and getting this error.

robsadams · 2024-01-13T22:14:06Z

Above they gave a thumbs up to .72.4 so I assume from that point on... I upgraded to .73 and have not seen it.... although I have not tried to recreate it.

softmarshmallow · 2024-01-17T09:37:51Z

Can anyone tell what this is regards to? which module is throwing this error? no clue, can't debug.

Nantris · 2024-02-23T00:42:09Z

Can anyone confirm what version this is fixed on? Or even that it really is fixed?

robertdue · 2024-02-26T13:54:31Z

Can anyone confirm what version this is fixed on? Or even that it really is fixed?

I have the same problem with 0.72.10

faisal-rehman19 · 2024-03-05T07:14:58Z

Facing the same issue with 0.73.1. Data from the server contains buffer data which might be the reason for this error.

gabriel-messas · 2024-03-05T18:29:21Z

0.73.4 still with error here

Nantris · 2024-03-05T20:39:47Z

@ishikawa are you sure this is fixed and should be closed?

DrRefactor · 2024-03-06T10:56:50Z

Observing the same issue on long running app in 0.72.6.

jack2684 · 2024-03-12T05:04:50Z

Same issue with 0.73.2

Nantris · 2024-03-12T19:41:25Z

@ishikawa would you please re-open this issue?

simon-accesso · 2024-03-14T08:44:33Z

@ishikawa would you please re-open this issue?

This! Observed with 72.6 and higher.

tribou · 2024-03-17T21:41:27Z

facebook/hermes#851 may be related

Nantris · 2024-03-18T20:00:49Z

@tribou yes I think so. Good find.

therbta · 2024-03-28T19:48:18Z

I'm facing the same issue on Android.

daveyd80 · 2024-05-30T11:15:44Z

Same Issue here 0.73.1 in a long running app. Issue needs re-opening please!

RangeError: Property storage exceeds 196607 properties

This error is located at:
    in Unknown (created by LogBoxInspectorSourceMapStatus)
    in RCTView (created by View)
    in View (created by LogBoxButton)
    in TouchableWithoutFeedback (created by LogBoxButton)
    in LogBoxButton (created by LogBoxInspectorSourceMapStatus)
    in LogBoxInspectorSourceMapStatus (created by LogBoxInspectorStackFrames)
    ...

arun057 · 2024-06-01T17:31:41Z

Facing the same issue on 0.74.1 with Hermes.

Med5KDB · 2024-06-06T21:24:44Z

Facing the same issue when trying to upload file to aws s3 (even if I think it's not related to file-upload action, seems to be related to the fetch

Mikail-1022063 · 2024-06-07T23:46:23Z

Facing the same issue, any updates on this? I also have a image upload, and somethimes after being a couple of minutes afk in the app i get this error Property storage exceeds 196607 properties

inkCrazy · 2024-06-17T05:57:34Z

Has the problem been solved？

iamsreeragkp · 2024-06-20T09:02:45Z

Still facing this problem in 0.73.0

danyalutsevich · 2024-06-24T15:50:44Z

What can be the cause of this error?
Im having this error in react-native 0.74.2
Im using expo 51.0.14

Nantris · 2024-06-24T18:16:54Z

What can be the cause of this error?

I believe the cause is that objects can only support a maximum of 196607 properties in the Hermes engine

NewvilleMedia · 2024-07-07T16:30:14Z

I get this error when the simulator is open and I let it sit idle for a bit.

Dat-Mobile · 2024-07-10T12:36:12Z

For me I console.log the Buffer variable, removed it and now working fine

AlastairTaft · 2024-07-23T08:05:34Z

For me I console.log the Buffer variable, removed it and now working fine

Thank you, you've saved me a headache

f1shy-dev · 2024-07-25T14:13:02Z

For me I console.log the Buffer variable, removed it and now working fine

Can you show details of this implementation/fix? What do you mean?

AlastairTaft · 2024-07-26T00:56:03Z

For me I console.log the Buffer variable, removed it and now working fine

Can you show details of this implementation/fix? What do you mean?

Console logging on an extremely large array causes the error / crash. Which makes sense.

jeafgilbert · 2024-07-26T02:04:08Z

I used clone function from 'lodash', got the same error. Now working fine after switch to ramda.

ywisax · 2024-08-11T13:05:01Z

Same problem in react-native 0.74.5

stdiodavid · 2024-09-03T05:29:00Z

Same problem in React Native v0.75.2

landabaso · 2024-09-03T07:26:57Z

Hi @ishikawa,

I see that several users, including myself, are still facing this issue in the latest versions. Would you consider reopening this issue to raise awareness and revisit the problem?

Thank you!

Whitelistedd · 2024-09-12T10:43:01Z

also experiencing the same thing

bumpingChris · 2024-09-22T06:23:14Z

I'm experiencing the same thing too

just-dodo · 2024-09-24T06:51:57Z

experiencing the same thing

ishikawa · 2024-09-25T23:14:20Z

Apologies for the delay in responding. Since the fix I proposed was merged, I have not been able to reproduce the issue when using fetch, and I believe the PR resolved the problem. Our app has been running for over a year since the issue, and we haven't encountered the same problem.

I also updated my previous reproduction code to the latest Expo SDK 51 (w/ react-native 0.74.5), but the issue still does not reproduce.

https://github.com/ishikawa/react-native-fetch-property-storage-exceeds-error

While I don’t have much capacity to dive deeper into this, if anyone is seeing this issue with fetch under different conditions, it would be interesting to hear more details.

angelopedroso · 2024-10-04T19:05:57Z

I'm using tanstack query to do a get requisition from 5 to 5s, after 6h (maybe), emit this error. 0.73.6. I'm using axios with react query

XantreDev · 2024-10-07T18:21:41Z

React native: 0.73.6

function App() {
  useEffect(() => {
    const tenMb = new Uint8Array(10 * 1024 * 1024);
    const formData = new FormData();
    formData.append("0", tenMb);

    fetch("https://www.google.com/", {
      method: "POST",
      body: formData
    })
      .then(res => {
        console.log("successfully send 10mb", res);
      })
      .catch(err => {
        console.log("failed to send 10mb", err);
      });
  }, []);
  return null

 LOG  failed to send 10mb [RangeError: Property storage exceeds 196607 properties]

This is because Uint8Array is not converted to Blob. If convert - it works

yMosk · 2024-10-11T16:42:50Z

any news on how to fix this?

vitordesouza · 2024-11-14T10:55:07Z

This does not seem to be exclusively related to fetch.
I am getting this error simply by leaving the app running, no requests, no usage. Couple hours in standby and I get this error. React native 0.74.5

edgarciametro · 2024-11-14T16:28:00Z

This does not seem to be exclusively related to fetch. I am getting this error simply by leaving the app running, no requests, no usage. Couple hours in standby and I get this error. React native 0.74.5

this is my exact experience, started a new build and for now it is gone.

fistofzen · 2024-11-17T08:52:05Z

same for me

This does not seem to be exclusively related to fetch. I am getting this error simply by leaving the app running, no requests, no usage. Couple hours in standby and I get this error. React native 0.74.5

this is my exact experience, started a new build and for now it is gone.

Nantris · 2024-11-17T19:08:14Z

I think people are not understanding this is related to the maximum properties an object can have. Make an enormous array and log it out and you'll face this problem too.

fistofzen · 2024-11-18T06:18:08Z

I think people are not understanding this is related to the maximum properties an object can have. Make an enormous array and log it out and you'll face this problem too.

I dont have any case like that.

vitordesouza · 2024-11-22T14:23:16Z

I think people are not understanding this is related to the maximum properties an object can have. Make an enormous array and log it out and you'll face this problem too.

Yes, that may be true. The problem is that the identity of the hypothetical enormous array is a mistery.

I don't deal with big objects or big amounts of data in my own code.
The error occurs independently from the usage at random moments which makes it impossible to reproduce/debug.

ishikawa added the Needs: Triage 🔍 label Sep 14, 2023

github-actions bot added the 🌐Networking Related to a networking API. label Sep 14, 2023

cortinico added the Issue: Author Provided Repro This issue can be reproduced in Snack or an attached project. label Sep 14, 2023

ishikawa mentioned this issue Sep 19, 2023

Use Map instead of object in BlobRegistry #39528

Closed

ishikawa closed this as completed Sep 20, 2023

JunielKatarn mentioned this issue Oct 20, 2023

Implement BlobCollector microsoft/react-native-windows#12269

Merged

mark-prins mentioned this issue Dec 5, 2023

App crashing after a few days or a few hours msupply-foundation/msupply-cold-chain#241

Open

softmarshmallow mentioned this issue Jan 16, 2024

CocoaPods could not find compatible versions for pod "React-FabricImage" #42296

Closed

"Property storage exceeds 196607 properties" error when using fetch more than a certain number of times in React Native #39441

"Property storage exceeds 196607 properties" error when using fetch more than a certain number of times in React Native #39441

Comments

ishikawa commented Sep 14, 2023

Description

Our solution

React Native Version

Output of npx react-native info

Steps to reproduce

Snack, screenshot, or link to a repository

ishikawa commented Sep 19, 2023

ishikawa commented Sep 20, 2023

robsadams commented Sep 29, 2023 • edited Loading

Ladvace commented Dec 24, 2023

robsadams commented Jan 5, 2024

brunomartins-com commented Jan 13, 2024

robsadams commented Jan 13, 2024

softmarshmallow commented Jan 17, 2024

Nantris commented Feb 23, 2024

robertdue commented Feb 26, 2024 • edited Loading

faisal-rehman19 commented Mar 5, 2024 • edited Loading

gabriel-messas commented Mar 5, 2024

Nantris commented Mar 5, 2024

DrRefactor commented Mar 6, 2024

jack2684 commented Mar 12, 2024 • edited Loading

Nantris commented Mar 12, 2024

simon-accesso commented Mar 14, 2024

tribou commented Mar 17, 2024

Nantris commented Mar 18, 2024

therbta commented Mar 28, 2024

daveyd80 commented May 30, 2024

arun057 commented Jun 1, 2024

Med5KDB commented Jun 6, 2024

Mikail-1022063 commented Jun 7, 2024

inkCrazy commented Jun 17, 2024

iamsreeragkp commented Jun 20, 2024

danyalutsevich commented Jun 24, 2024

Nantris commented Jun 24, 2024

NewvilleMedia commented Jul 7, 2024

Dat-Mobile commented Jul 10, 2024

AlastairTaft commented Jul 23, 2024

f1shy-dev commented Jul 25, 2024

AlastairTaft commented Jul 26, 2024

jeafgilbert commented Jul 26, 2024 • edited Loading

ywisax commented Aug 11, 2024

stdiodavid commented Sep 3, 2024

landabaso commented Sep 3, 2024

Whitelistedd commented Sep 12, 2024

bumpingChris commented Sep 22, 2024

just-dodo commented Sep 24, 2024

ishikawa commented Sep 25, 2024 • edited Loading

angelopedroso commented Oct 4, 2024

XantreDev commented Oct 7, 2024 • edited Loading

yMosk commented Oct 11, 2024

vitordesouza commented Nov 14, 2024

edgarciametro commented Nov 14, 2024

fistofzen commented Nov 17, 2024

Nantris commented Nov 17, 2024

fistofzen commented Nov 18, 2024

vitordesouza commented Nov 22, 2024 • edited Loading

"Property storage exceeds 196607 properties" error when using `fetch` more than a certain number of times in React Native #39441

"Property storage exceeds 196607 properties" error when using `fetch` more than a certain number of times in React Native #39441

Output of `npx react-native info`

robsadams commented Sep 29, 2023 •

edited

Loading

robertdue commented Feb 26, 2024 •

edited

Loading

faisal-rehman19 commented Mar 5, 2024 •

edited

Loading

jack2684 commented Mar 12, 2024 •

edited

Loading

jeafgilbert commented Jul 26, 2024 •

edited

Loading

ishikawa commented Sep 25, 2024 •

edited

Loading

XantreDev commented Oct 7, 2024 •

edited

Loading

vitordesouza commented Nov 22, 2024 •

edited

Loading