René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Problem using JSTypedArray","articleBody":"Hello, I ran into a problem using JSTypedArray and was wondering if you could give me some help.\r\n\r\nI read through the blog [here](https://phoboslab.org/log/2015/11/the-absolute-worst-way-to-read-typed-array-data-with-javascriptcore) and figured it out it could not solve my problem, but wondering if you might have ran into the same problem. I used an `ArrayBuffer` to transfer large amount of data from js to C, but the result is sometimes wrong. When I set a value in js, the underlying memory is untouched. for example\r\n\r\n```js\r\nlet arr = ... // arr is a Uint8Array\r\narr[0] = 1;\r\narr[1] = 2;\r\narr[2] = 3;\r\narr[3] = 4;\r\nconsole.log(arr[0], arr[1], arr[2], arr[3]); // 1 2 3 4\r\nconsole.log('' + arr); // something other than 1,2,3,4\r\nconsole.log(arr[0], arr[1], arr[2], arr[3]); // something other than 1 2 3 4\r\n```\r\n\r\nIt happens randomly, cannot be reproduced every time. The key is that when I made a native call, such as passing the TypedArray object into a native function, or calling `toString` of the typed array, the array then acts normally. Even if the native function does nothing with the array (such as `JSObjectGetTypedArrayBytesPtr`).\r\n\r\nI sincerely hope that you could give some guidance about how to avoid this bug, many thanks.","author":{"url":"https://github.com/kyriosli","@type":"Person","name":"kyriosli"},"datePublished":"2019-01-07T08:10:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/37/JavaScriptCore-iOS/issues/37"}