Open ErikBooij opened 10 months ago
Running
rm -rf .parcel-cache
and starting the watcher again, resolves this.
True for my use case too. Also, by making this comment hopefully it'll catch more attention for others who stumble in here from their seg faults.
Indeed I have the same issue, and this is for a rather simple library build. Having the cache causes segfault.
Having this exact same issue. Only using parcel through GoWebly, but whether I do run or build, I always get a segmentation fault.
I'm also on macOS (15 dev beta) with a M1 Pro, just as #7402 and this issue probably too I think. #9670 is also likely related.
Deleting .parcel-cache
indeed fixed the issue for now, but I guess it's worth looking into actually fixing this - unluckily I have no clue about parcel itself, but could provide debug information if told how to enable.
Try adding a manual resolution to @parcel/watcher@v2.4.2-alpha.0
It includes parcel-bundler/watcher#177, which should fix some memory bugs in the watcher code.
You'll need to add this to your package.json
file:
"resolutions": {
"@parcel/watcher": "v2.4.2-alpha.0"
Hi 👋
Although I've stated in the title that I'm experiencing this on 2.10.3, I was experiencing this on prior versions too. Any time I restart the Parcel watcher, while a populated
.parcel-cache
folder is present, I get aSegmentation fault: 11
error. I regularly need to restart the watcher, because Parcel complains (in the browser) that it cannot find a file (not sure if it's related to the segfault). Runningrm -rf .parcel-cache
and starting the watcher again, resolves this.The command I'm running, is:
This yields (when I'm running it as a Make command):
or this when I run it directly:
This is my
package.json
I do not use a Parcel config file, but I do have a
tailwind.config.js
, and a.postcssrc
:🌍 Your Environment