301701 2025-10-30 09:44:14 -0700 range request to blob url created from URL.createObjectURL does not work in Safari but works in Chrome 2025-10-31 10:12:25 -0700 1 1 1 Unclassified WebKit New Bugs Safari Technology Preview All All RESOLVED INVALID P2 Major --- 1 andrewhodel webkit-unassigned ap oldest_to_newest 2155278 0 andrewhodel 2025-10-30 09:44:14 -0700 https://jsfiddle.net/7h016nke/ 2155280 1 andrewhodel 2025-10-30 10:02:02 -0700 It can be accomplished with ReadableStream but fetch should also work correctly. https://jsfiddle.net/dw2vkj7h/ 2155314 2 ap 2025-10-30 13:31:59 -0700 Thank you for the report! I cannot reproduce this using STP 230, <https://jsfiddle.net/7h016nke/> logs `"bytes=7-11", [object ArrayBuffer]` in console. And when I decode the content, I see the correct bytes from the file. 2155351 3 andrewhodel 2025-10-30 15:00:05 -0700 @comment #2 It's a good thing this conversation is being documented. You need to load much data and eventually Safari starts to log an error in the console that is a specific WebKit error from URL.createObjectURL when you try to load files after that. 2155356 4 andrewhodel 2025-10-30 15:02:56 -0700 I wrote more about it here - https://medium.com/@andrewhodel/read-files-to-arraybuffer-without-delay-or-memory-usage-in-every-browser-aede7b3d9c2a 2155365 5 ap 2025-10-30 15:17:52 -0700 Can you please provide steps to reproduce that actually demonstrate the issue? How much data is much data? Is it large files or selecting multiple files sequentially? 2155494 6 andrewhodel 2025-10-31 06:17:16 -0700 I don't know why you don't understand that it does the same thing to you as it does to me. I've already removed using fetch and replaced it with using streams because of this issue. I think the only reasonable attempt at answering that is that someone who is familiar with that process in the WebKit codebase evaluate the routine with focus on how this could happen to answer that question. That's why it is a bug report, do you think that I am lying to you for fun and entertainment? 2155523 7 ap 2025-10-31 08:20:29 -0700 Please provide steps to reproduce, then we can take a look. 2155543 8 andrewhodel 2025-10-31 09:53:58 -0700 @comment #7 I did, I didn't provide time to actualize those steps because it is a very long time. I also told you that it would be less time and more importantly effort to: "I think the only reasonable attempt at answering that is that someone who is familiar with that process in the WebKit codebase evaluate the routine with focus on how this could happen to answer that question." Andrew 2155548 9 ap 2025-10-31 10:09:30 -0700 I hear you that you are observing a problem. The test does not reproduce it, so it could be a WebKit bug or a bug in your production code, either way, there is nothing to investigate based on the provided information. 2155549 10 andrewhodel 2025-10-31 10:12:03 -0700 The test does reproduce it, you just didn't test enough as I already explained. It doesn't matter, it's been documented and is searchable and through time more people will reply to the bug if they experience it. That increases it's credibility. It should not have been closed because it does not infringe on any constitutional rights, that is your mistake and it is also documented. Andrew 2155550 11 andrewhodel 2025-10-31 10:12:25 -0700 The test does reproduce it, you just didn't test enough as I already explained. It doesn't matter, it's been documented and is searchable and through time more people will reply to the bug if they experience it. That increases it's credibility. It should not have been closed because it does not infringe on any constitutional rights, that is your mistake and it is also documented. Andrew