Timo

```js const ivm = require('isolated-vm'); const isolate = new ivm.Isolate(); const ctx = isolate.createContextSync(); function load() { return ctx.eval(` const u8 = new Uint8Array([0,97,115,109,1,0,0,0,1,7,1,96,2,127,127,1,127,3,2,1,0,5,3,1,0,17,7,16,2,6,109,101,109,111,114,121,2,0,3,97,100,100,0,0,10,9,1,7,0,32,0,32,1,106,11,11,10,1,0,65,128,128,192,0,11,1,4,0,131,1,9,112,114,111,100,117,99,101,114,115,2,8,108,97,110,103,117,97,103,101,1,4,82,117,115,116,0,12,112,114,111,99,101,115,115,101,100,45,98,121,3,5,114,117,115,116,99,37,49,46,54,48,46,48,45,110,105,103,104,116,108,121,32,40,50,50,101,52,57,49,97,99,55,32,50,48,50,50,45,48,49,45,49,51,41,6,119,97,108,114,117,115,6,48,46,49,57,46,48,12,119,97,115,109,45,98,105,110,100,103,101,110,18,48,46,50,46,56,48,32,40,52,99,97,97,57,56,49,54,53,41]); WebAssembly.instantiate(u8).then(x => x.instance.exports.add(5, 6)); `, {...

Timeout is ignored when creating very large `BigInt`s

35

If a timeout is provided and supplied code ends in an infinite loop or similar so that it exceeds this limit, an error saying 'Script execution timed out' is thrown....

To speed up startup times, it may be useful to make it possible to snapshot the JavaScript heap and compiled bytecode. - [x] Bytecode ([snapshot branch](https://github.com/y21/dash/tree/snapshot)) - [x] Serialize -...

```js let z = {}; let y = {__proto__:z}; z.__proto__ = y; y.a ``` running this crashes dash with a stack overflow because it gets stuck in a recursive "loop"...

Generated JS code can end up with (reserved) keywords as identifiers

3

It seems wasm-bindgen does not check that identifiers that are valid in Rust code might not be valid in JavaScript. Building a project containing a function like this: ```rs use...

Very long "reference chains" (i.e. very deeply nested objects) can overflow the stack because, afaict, each object trace during GC cycles is its own function call. It seems like there's...

https://github.com/denoland/rusty_v8/blob/64ce32392a680695975a7d40921f11d1e4bbf7c5/src/inspector.rs#L275-L281 https://github.com/denoland/rusty_v8/blob/64ce32392a680695975a7d40921f11d1e4bbf7c5/src/inspector.rs#L538-L544 The call to `.base()` here on line 281 (and line 544) creates a reference to an uninitialized `T`, because `base()` is defined to take `&self` as its receiver....

`Isolate::set_host_import_module_dynamically_callback` is unsound

1

This function takes a [`HostImportModuleDynamicallyWithImportAssertionsCallback`](https://docs.rs/rusty_v8/0.30.0/rusty_v8/type.HostImportModuleDynamicallyWithImportAssertionsCallback.html). It's a callback that is called to resolve `import()`s, and should return a *raw* pointer to a `v8::Promise`. Its safety invariants are (sort of) mentioned...

The string `1/0` causes a panic when fed to `cron::Schedule::from_str` (0.11.0): ```rs thread 'testing' panicked at 'assertion failed: step != 0', /rustc/6dd68402c5d7da168f87d8551dd9aed1d8a21893/library/core/src/iter/adapters/step_by.rs:21:9 stack backtrace: 0: rust_begin_unwind at /rustc/6dd68402c5d7da168f87d8551dd9aed1d8a21893/library/std/src/panicking.rs:584:5 1: core::panicking::panic_fmt...

It's currently possible to misuse the `dyn_push!` macro in various ways. This PR tries to prevent the ones I found: - `$stack:expr` metavariable is expanded in unsafe block. This allows...