Parcel sometimes fails to start properly #1342

wyhaya · 2018-05-11T07:06:30Z

🐛 bug report

He can sometimes work, sometimes he can't work.

When I remove the scss file it may improve, but I'm not sure if the problem is there.

Perhaps it is related to the loading mechanism of the module?

Faster processing when there are fewer modules, When the number of modules is large, the dependency is more complicated and the relationship is not handled properly, Causes the process to exit abnormally.

🎛 Configuration (.babelrc, package.json, cli command)

{
  "name": "parcel",
  "version": "1.0.0",
  "scripts": {
    "dev": "parcel ./src/view/*.html"
  },
  "devDependencies": {
    "node-sass": "^4.9.0",
    "parcel-bundler": "^1.8.1"
  }
}

🤔 Expected Behavior

Normal start work

😯 Current Behavior

Sometimes quit abnormally

Comparison of loading scss files and removing scss

🔦 Context

parcel ./src/view/*.html

yarn run v1.5.1
$ parcel ./src/view/*.html
Server running at http://localhost:1234
⏳  Building hmr-runtime.js...
error An unexpected error occurred: "Command failed.
Exit signal: SIGSEGV
Command: sh
Arguments: -c parcel ./src/view/*.html
Directory: /Users/WYH/Desktop/parcel
Output:
".
info If you think this is a bug, please open a bug report with the information provided in "/Users/WYH/Desktop/parcel/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

💻 Code Sample

index.html :

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>Title</title>
    <link rel="stylesheet" href="../style/index.scss">
</head>
<body>
  hello world
</body>
</html>

base.scss :

body{
  background: red;
}

index.scss :

@import './base.scss';
.btn{
    width: 100px;
    height: 38px;
    border: 1px solid #ae2616;
    color: #ae2616;
    outline: none;
    background-color: transparent;
    cursor: pointer;
}

🌍 Your Environment

Software	Version(s)
Parcel	1.8.1
Node	9.9.0
npm/Yarn	1.5.1
Operating System	macOS High Soerra `10.13.4`

The text was updated successfully, but these errors were encountered:

tsiq-swyx · 2018-05-13T00:40:28Z

i get this too in my create-react-app-parcel project. (just the base template, nothing fancy at all). its super weird, 1 out of 20 times it will run. there is a segfault somewhere and I don't know how to debug it further:

tsiq-swyx · 2018-05-13T01:01:54Z

after doing something else for awhile and then coming back, this problem goes away. so there seems to be some memory lock on something that then gets garbage'd away? not really knowing the internals of parcel I don't even know how to track this down further than the SIGSEGV error.

wyhaya · 2018-05-13T03:47:04Z

This problem does not occur when using parcel build

tsiq-swyx · 2018-05-13T21:42:33Z

right, so its a parcel or parcel watch problem. i still can't track it down but its more intermittent for me now. any one have ideas on how to reliably reproduce this kind of segfault error?

wyhaya · 2018-05-14T01:34:50Z

DeMoorJasper · 2018-05-14T08:23:53Z

~~I'm currently having this same issue again, I'm 99% sure this is a SASS issue, as it only happens once I've added scss files to my build pipeline.~~

EDIT: Just converted my sass styles into less styles and it still fails, but at least it's not consistent now

This is a full stacktrace I've managed to extract using segfault-handler

PID 88808 received SIGSEGV for address: 0x0
0   segfault-handler.node               0x00000001022f0168 _ZL16segfault_handleriP9__siginfoPv + 280
1   libsystem_platform.dylib            0x00007fff7ecc2f5a _sigtramp + 26
2   ???                                 0x000000010fdac088 0x0 + 4560961672
3   fse.node                            0x00000001022d8467 _ZN3fse8FSEventsD2Ev + 91
4   fse.node                            0x00000001022d8514 _ZN3fse8FSEventsD0Ev + 14
5   node                                0x00000001004ca603 _ZN2v88internal13GlobalHandles31DispatchPendingPhantomCallbacksEb + 147
6   node                                0x00000001004ca931 _ZN2v88internal13GlobalHandles31PostGarbageCollectionProcessingENS0_16GarbageCollectorENS_15GCCallbackFlagsE + 49
7   node                                0x00000001004e0399 _ZN2v88internal4Heap24PerformGarbageCollectionENS0_16GarbageCollectorENS_15GCCallbackFlagsE + 2665
8   node                                0x00000001004df2b5 _ZN2v88internal4Heap14CollectGarbageENS0_15AllocationSpaceENS0_23GarbageCollectionReasonENS_15GCCallbackFlagsE + 853
9   node                                0x00000001004a0992 _ZN2v88internal7Factory15NewFillerObjectEibNS0_15AllocationSpaceE + 82
10  node                                0x000000010076a665 _ZN2v88internal26Runtime_AllocateInNewSpaceEiPPNS0_6ObjectEPNS0_7IsolateE + 101
11  ???                                 0x00001a12704042fd 0x0 + 28666494993149

If everyone in this issue is using MAC OS X I think this is an fsevents bug?
fse.node appears to be a file related to fsevents

DeMoorJasper · 2018-05-14T13:46:27Z

Might be related to this issue: fsevents/fsevents#218

tsiq-swyx · 2018-05-14T16:24:51Z

yes i'm using macosx.

i have a confession.. how do you use segfault-handler in the context of parcel? their readme doesn't exactly hold your hand through it...

DeMoorJasper · 2018-05-14T16:27:44Z

You simple put require('segfault-handler').registerHandler(); at the start of the bundler.js file
Than it throws the detailed report and writes that report to the cwd

tsiq-swyx · 2018-05-14T16:36:46Z

ok thanks. i cant replicate the segfault right now, will wait for the next time this happens.

…

On Mon, May 14, 2018 at 12:28 PM Jasper De Moor ***@***.***> wrote: You simple put require('segfault-handler').registerHandler(); at the start of the bundler.js file — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1342 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AiT1gpvi-41ssi3Ej8CPCkOBMwoZdUi6ks5tybCVgaJpZM4T7ALG> .

DeMoorJasper · 2018-05-14T17:13:16Z

No problem, I'll do a PR that should fix this in a few mins

trxcllnt · 2018-05-15T01:19:26Z

@tsiq-swyx also if you turn on core dumps at the start of a terminal session, you can use llnode to capture the JS backtrace and post the stack frame with unmasked JS frames, without segfault-handler (I've had issues with segfault-handler in node10 recently). This post is a good intro on how to use llnode to inspect the core dump: https://developer.ibm.com/node/2016/08/15/exploring-node-js-core-dumps-using-the-llnode-plugin-for-lldb/

I'm about to start a new project with create-react-app-parcel, and will post the stack trace here if I encounter this too.

tsiq-swyx · 2018-05-17T17:48:58Z

thanks, confusingly it just works every time now. hard to replicate this but i'll keep this issue open on c-r-a-p.

ewyler · 2018-06-10T20:12:24Z

When is the planned release date for the next version with the fix incorporated? This is consistently reproducible for me using the current latest version (1.8.1, same as in this original report).

JamesTheHacker · 2018-08-04T10:05:06Z

Exactly the same problem here. It's been happening a lot this morning.

fang0rnz · 2018-11-08T13:36:36Z

same problem here, as of november

fguillen · 2023-10-16T08:49:08Z

Same here:

> yarn build
yarn run v1.22.19
warning package.json: No license field
$ parcel build
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I am using parcel 2.11.0

fguillen · 2024-04-22T14:48:32Z

It is still happening in v2.12.0 :/

fguillen · 2024-04-22T14:50:04Z

Don't know if is not related, but moving to a parent directory and coming back to the project dir and the command worked :/

0x1af2aec8f957 · 2024-09-01T01:17:14Z

The problem still exists.

The following information may be useful:

node(42005,0x16fadf000) malloc: Incorrect checksum for freed object 0x13c0dfa00: probably modified after being freed.
Corrupt value: 0x3361636366393331
node(42005,0x16fadf000) malloc: *** set a breakpoint in malloc_error_break to debug
error Command failed with exit code 1.

This problem seems to be the same: #9926 .

DeMoorJasper added the 🐛 Bug label May 11, 2018

tsiq-swyx mentioned this issue May 13, 2018

known issue - sometimes segfaults on starts assuncaocharles/create-react-app-parcel#1

Closed

DeMoorJasper added the ✔️ Confirmed Bug label May 13, 2018

DeMoorJasper mentioned this issue May 14, 2018

Put filewatcher in a worker, for better stability and performance #1368

Merged

DeMoorJasper mentioned this issue May 16, 2018

I often encounter the "segmentation fault 11" problem #1374

Closed

devongovett closed this as completed in #1368 May 21, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Parcel sometimes fails to start properly #1342

Parcel sometimes fails to start properly #1342

wyhaya commented May 11, 2018 •

edited

Loading

tsiq-swyx commented May 13, 2018

tsiq-swyx commented May 13, 2018

wyhaya commented May 13, 2018

tsiq-swyx commented May 13, 2018

wyhaya commented May 14, 2018

DeMoorJasper commented May 14, 2018 •

edited

Loading

DeMoorJasper commented May 14, 2018

tsiq-swyx commented May 14, 2018

DeMoorJasper commented May 14, 2018 •

edited

Loading

tsiq-swyx commented May 14, 2018 via email

DeMoorJasper commented May 14, 2018

trxcllnt commented May 15, 2018

tsiq-swyx commented May 17, 2018

ewyler commented Jun 10, 2018

JamesTheHacker commented Aug 4, 2018

fang0rnz commented Nov 8, 2018

fguillen commented Oct 16, 2023 •

edited

Loading

fguillen commented Apr 22, 2024

fguillen commented Apr 22, 2024

0x1af2aec8f957 commented Sep 1, 2024 •

edited

Loading

Parcel sometimes fails to start properly #1342

Parcel sometimes fails to start properly #1342

Comments

wyhaya commented May 11, 2018 • edited Loading

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

🤔 Expected Behavior

😯 Current Behavior

🔦 Context

💻 Code Sample

🌍 Your Environment

tsiq-swyx commented May 13, 2018

tsiq-swyx commented May 13, 2018

wyhaya commented May 13, 2018

tsiq-swyx commented May 13, 2018

wyhaya commented May 14, 2018

DeMoorJasper commented May 14, 2018 • edited Loading

DeMoorJasper commented May 14, 2018

tsiq-swyx commented May 14, 2018

DeMoorJasper commented May 14, 2018 • edited Loading

tsiq-swyx commented May 14, 2018 via email

DeMoorJasper commented May 14, 2018

trxcllnt commented May 15, 2018

tsiq-swyx commented May 17, 2018

ewyler commented Jun 10, 2018

JamesTheHacker commented Aug 4, 2018

fang0rnz commented Nov 8, 2018

fguillen commented Oct 16, 2023 • edited Loading

fguillen commented Apr 22, 2024

fguillen commented Apr 22, 2024

0x1af2aec8f957 commented Sep 1, 2024 • edited Loading

wyhaya commented May 11, 2018 •

edited

Loading

DeMoorJasper commented May 14, 2018 •

edited

Loading

DeMoorJasper commented May 14, 2018 •

edited

Loading

fguillen commented Oct 16, 2023 •

edited

Loading

0x1af2aec8f957 commented Sep 1, 2024 •

edited

Loading