Devon Govett

resolved by #6640

@mattcompiles We discussed with @mischnic in the meeting today. Sounds like we will need a new value/mode for `asset.sideEffects` that indicates that the side effects only apply to that asset...

Unfortunately I think this is a breaking change. People would need to update their types in a lot of places, as shown in the examples in #6628. Also, input values...

I am not familiar with that system, but perhaps one of these conditions is not matching and therefore none of the platform specific code is being included? You could try...

I get errors in `v8::internal::StringTable::OffHeapStringHashSet::KeyIsMatch`. These occur in multiple different call stacks, e.g. in `napi_set_named_property`: ``` * thread #13, stop reason = EXC_BAD_ACCESS (code=1, address=0xa5fa) * frame #0: 0x000000010077e3f4 node`bool...

It appears that worker_threads may also be involved here. I cannot reproduce when I disable multi-threading in Parcel. Haven't managed to produce a smaller reproduction yet unfortunately...

I've reduced at least one of these cases down to a simple reproduction. It requires two typed arrays which are serialized using `v8.serialize`, and it crashes during `v8.deserialize`. ```js let...

Maybe you don't have proper permissions? Please provide a reproduction.

Can someone try running in a debugger (e.g. `lldb` or `gdb`) and report the backtrace where the segfault is occurring? We have not changed anything in Parcel so I'm wondering...

This seems like a possible v8 bug. I am seeing crashes in multiple different stack traces having to do with string handling. Hopefully they'll investigate soon. https://github.com/nodejs/node/issues/54573#issuecomment-2323042402