Sam Cao
Sure, I'll visit it sometime later. Better grab me at discord.
It's been so long. I just submitted a fix to the dev branch. Do you mind taking a try? The snapshot build is at Actions.
I reviewed your code. I saw there are roughly 3 threads: UI, script execution, debugger. I wonder if the root cause is: callback from V8 inspector falls into the UI...
The project you uploaded has some local dependencies so that I didn't fix them, but reviewed the code only. Could you upload a revised one for me to debug?
I reviewed the latest code. I wonder if you might miss some key steps while playing with the V8 inspector.
Good question. Most of Javet users virtualize the module system with absolute module path so that the referrer is always ignored. And, yes, I think the case you present is...
I checked the code. Here's my finding. The referrer exists, but the resource name is always null because V8 doesn't provide that. The official solution is to keep a `Map`...
I thought it over and found out: It's right for V8 not to carry resource name with the module because the referrer's resource name may change based on the relative...
Good news! I enhanced `V8Module.getResourceName()` so that it can return the actual module name. V8 stores the module name somewhere, but doesn't want to expose it. I had to dig...
There are generally 2 approaches. 1. One `.so` file per CPU arch - You don't need to package all 4 `.so` files. That will reduce the size by 3/4. 2....