Closed ccloli closed 3 years ago
Relaunching Chrome cannot fix the bug, with Chrome 84.0.4147.135 (64-bit).
I'm out at this time, I almost used up my image limits, these images are too large lol
(Though they're not that large if you enabled compression, 12MB → ≤2MB)
Well... It's stranged that ViolentMonkey v2.12.7 on Chrome seems work fine, however the image downloaded by ViolentMonkey is empty at 0KB. Both Blob storage and FileSystem are the same.
At this time, it seems that it's not a bug of extension, but Chrome?
This bug should be fixed in Tampermonkey BETA v4.12.6124 and ViolentMonkey v2.12.8.
Tampermonkey has released v4.12 to stable channel, this issue should be fixed for most users soon.
Not sure why this happens, but it may be a bug of Tampermonkey?
From the background page of Tampermonkey, it's sure that
003.png
,017.png
and020.png
is done (the timeline detail doesn't say the request is not finished). However theonload
callback ofGM_xmlhttpRequest
is never called, I added some breakpoints anddebugger
statement, but none of them are called.At this time, I only found https://exhentai.org/g/1713713/ccbaeb3112/ can reproduce the bug, it'll break on these 3 images. When I try downloading another gallery, the debugger is called.
Relaunch Tampermonkey and open a new tab cannot fix the bug.
The bug can be reproduced with Tampermonkey 4.10 and Tampermonkey BETA 4.11.6118 on Chrome.
ViolentMonkey v2.12.7 on Chrome, and Tampermonkey 4.11.6117 on Firefox are fine, both of them can download the file and not stuck at 0KB/s.Maybe an upstream bug of Tampermonkey or Chrome?