Meteor segfault randomly on reload (localy) #8648
Comments
|
same here after upgrade, the error is the same: Client modified -- refreshing (x5)[1] 20587 segmentation fault meteor -s settings.json changing the numer - 20587 now but also many others like: 19119, 16496. |
|
@hwillson I think this is related to one or more of #8002 #6241 #4446 Seems a lot more people are reporting these lately so it may be time to take a proper look. The difficulty will probably be replicating the issue reliably without being able to access confidential code, I'm happy to help if I can though. Edit: Just for info, I see |
|
I'm having the same issue, and people are reporting it on the forums too. |
|
@hwillson - There is no error, just a "segmentation fault (core dumped)" message from the system. Don't know if this is relevent. I can add also that i work alot on backside (server files), the mac user works on front & back, and the debian user mostley on front. But i noticed that the problem happens either on reloading server and client files. I stay available if i can bring more clue about this. Thanks for your time. |
|
Thanks all - these comments really help. Please keep posting any additional details you uncover. |
|
Would it be possible for anyone getting a core dump here to share that core dump? |
|
Hi @hwillson, I'm experiencing the issue as well on macOS. About twice a day. |
|
Just had seg fault 11 happen three times within 10 minutes. This is seriously harming productivity. |
|
It would be preferable for anyone "+1"-ing this to, at the very least, include the version of Meteor that they're using. While important when reporting any bug, it's particularly important on an issue of this nature as it could be tied to any number of underlying dependencies (Node.js, v8, etc.) @rlora Your issue looks like a dangling pointer. If you're not doing manual memory management and relying on V8's automatic garbage collection, then it could certainly seem to be a V8 issue. As stated above, the Meteor version you're using would be helpful. Of course, there are no guarantees that any of the faults in this thread are related, but you're in an opportune position if you've captured it while attached. Can you get any more information from |
|
here is occuring several times almost on every change on code and meteor restarts... |
|
1.4.4.2 here as well. |
|
@abernix I'm sorry, I'm trying to replicate the crash but I've spent the whole afternoon trying and works like a charm :( I'm not doing manual memory management. I think the issue is in V8. I'm using For people experiencing the crash in macOS follow this steps:
Continue working in your app, if it crashes You can debug it from there. If you type I will continue trying to reproduce but maybe someone will capture it sooner. |
|
Helpful info @rlora, I'll run lldb today and see if I can come up with anything useful |
|
Who wants to decipher this? |
|
The previous comment was a seg fault 11 on one app, I think this one was an abort trap 6 on a different app: It looks like the meteor tool crashes first, followed by the actual app... Output of ps aux | grep node | grep ZZZ: meteor-tool: the app: |
|
@mjmasn Thanks for providing that. That does look like it's stemming from the |
|
@abernix: yep, yep and yep ;) Another possibly related issue (relating to gulp so could be another vote for this being a file watching issue): nodejs/node#10163. This could definitely be a bug in node / libuv... Is there anything I can do to dig deeper into this? I'm out of the country for a week without my laptop after today but happy to do anything that might help at the back end of next week :) |
|
@mjmasn Node 6 still uses the same version of |
|
i got that with lldb: Process 65164 stopped
(lldb) continue
|
|
@abernix I was able to catch a couple of segmentation faults but the signal I'm getting is different: This is the frame: |
|
I just notice that right now I got the segmentation falt when tried to load a template from another one and it has a typo in the name - I wrote "+loading" and it was "+loadingView" I'm using jade instead html |
|
|
|
@arggh That's unfortunate, though I know it's certainly fixed other segmentation faults so your particular case must be different. If you run I'd also suggest trying Meteor 1.6 beta releases if that's an option for you! |
|
Testing on 1.5.2-rc.2, will edit with results. EDIT: So far so good, we had really frequent segmentation faults and haven't had any yet |
|
I would say that this issue is lessened with Meteor 1.5.2, but that we're not out of the woods. Specifically, I believe the crash should be fixed thanks to #9031, however, there does seem to be another issue (also in similar V8 garbage-collection code) which (based on information I've analyzed privately with @arggh) appears to be the same as nodejs/node#3715 and https://bugs.chromium.org/p/chromium/issues/detail?id=408380 which have both been dismissed upstream due to lack of reproduction. Anyone continuing to experience crashes with Meteor 1.5.2, please do write back and provide any additional information you might have about your segmentation fault. If you're on macOS, consider posting (as a Gist and linking here) the file generated in I'll leave this particular issue open until @arggh or I are able to write up a new issue for the |
|
Hmm, I'm seeing this a few times a day now too (OSX): Updating to 1.5.2 now, will report back if issue persists. |
|
@danwild and others: If you're experiencing this problem on a regular basis, as a matter of experimentation would you please try running setting the On macOS this can be done with: $ TOOL_NODE_FLAGS="--no-expose-gc" meteor ... # usual arguments here.Reason being: the comments I listed here. Meteor does use the By passing /cc @arggh this should be an easier way of accomplishing the same change I had you make to your |
|
Oh, and please do report back with your findings, @danwild! |
|
Well, two days of dev since upgrading to Meteor |
|
@danwild Is that with the |
|
Just the meteor 1.5.2 update @abernix, hadn't seen the error again so didn't seem to need |
|
+1 on Meteor 1.5.0. Today, I got the SIGABRT for the first time without any reload, it occured after the server received data via the websockets connection (method call). |
|
I'm getting segmentation faults in production looks like code that uses Set and Map. |
|
@sirpy, I don't have the answer, but I'm interested in it. Could you show some example code: Set/Map from what? |
|
I think i isolated the crashes to a section in the code of a cronjob(using
syncedcron package) were the changes before it started crashing was
switching from regular javascript arrays/objects to new javascript Set/Map
objects.
…On Sun, Oct 22, 2017 at 10:32 PM, Michael Cole ***@***.***> wrote:
@sirpy <https://github.com/sirpy>, I don't have the answer, but I'm
interested in it. Could you show some example code: Set/Map from what?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8648 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAo9d7bPbDbASyuRerqVc57BXTxFAQnLks5su5hjgaJpZM4NLsae>
.
|
|
I've tried running the server with meteor patched node 4.8.4, (meteor node main.js) and the segmentation fault crashes stopped. |
|
Reporting just in case: Meteor 1.6.1 and still getting |
|
@arggh Was this with a deployed version of a Meteor 1.6.1 app? (That is to say, a built app being ran with |
|
@abernix Nope, they happen during local development. I haven't yet deployed with Meteor 1.6.x to any actual live app, should I expect/fear these crashes to appear in the deployed version with 1.6.1? |
|
I started facing this from today - happens every 10 mins approx. I did not do a meteor update today, just a ubuntu update (I am on Bionic beta), so it is highly likely that the cause is os specific, esp. since I am also getting chrome segfaults. Still, since I am at a loss on figuring out a fix, any help would be totally appreciated.
|
|
I also detect it's OS specific also it's directly indicating with Session Package? |
|
It still happens on the latest 1.8.0.2 release |
and others
Hi,
When i use meteor locally, server start correctly but I face frequent segfault which appear randomly (i cant figure exactly what cause it).
It seems to occure when server reload (due to a file modification). But doesn't segfault on every reload, and doesn't segfault on same files (sometimes modificaiton on server side, sometimes on client side).
My RAM isn't full (about 10Gb free when segfault occure).
And here is all package i use :
`meteor-base@1.0.4 # Packages every Meteor app needs to have
mobile-experience@1.0.4 # Packages for a great mobile UX
mongo@1.1.16 # The database Meteor supports right now
blaze-html-templates@1.0.4 # Compile .html files into Meteor Blaze views
reactive-var@1.0.11 # Reactive variable for tracker
jquery@1.11.10 # Helpful client-side library
tracker@1.1.2 # Meteor's client-side reactive programming library
standard-minifier-css@1.3.4 # CSS minifier run for production mode
standard-minifier-js@2.0.0 # JS minifier run for production mode
es5-shim@4.6.15 # ECMAScript 5 compatibility for older browsers.
ecmascript@0.7.2 # Enable ECMAScript2015+ syntax in app code
shell-server@0.2.3 # Server-side component of the
meteor shellcommandaccounts-ui@1.1.9
kadira:flow-router
zimme:active-route
underscore@1.0.10
kadira:blaze-layout
accounts-password@1.3.5
accounts-facebook@1.1.1
accounts-google@1.1.2
google-config-ui@1.0.0
facebook-config-ui@1.0.0
twbs:bootstrap
tanis:bootstrap-social
fortawesome:fontawesome
less@2.7.9
email@1.2.0
check@1.2.5
meteorhacks:ssr
arillo:flow-router-helpers
cfs:filesystem
ostrio:files
session@1.1.7
dburles:google-maps
sergeyt:typeahead
raix:handlebar-helpers
dburles:collection-helpers
manuel:reactivearray
aldeed:collection2-core
mizzao:bootboxjs
meteorhacks:aggregate
aldeed:autoform@6.0.0
summernote:summernote
anback:bootstrap-validator
aldeed:autoform-bs-datepicker
natestrauser:select2
rajit:bootstrap3-datepicker
natestrauser:font-awesome
mystor:device-detection
reactive-dict@1.1.8
aldeed:simple-schema
froala:editor
andrasph:clockpicker
aldeed:template-extension
tsega:bootstrap3-datetimepicker
`
I don't know which other informations i can give you, but i stay availabale if u need anything.
Regards.
The text was updated successfully, but these errors were encountered: