wohali opened a new issue #551: [Jenkins] couchjs segfaults URL: https://github.com/apache/couchdb/issues/551 ## Expected Behavior `couchjs` shouldn't segfault. ## Current Behavior Sometimes, in an automated run, it does. Here's an example: ```python test/javascript/tests/attachment_views.js Error: {exit_status,139} Trace back (most recent call first): 548: test/javascript/couch.js CouchError([object Object]) 511: test/javascript/couch.js ([object CouchHTTP]) 177: test/javascript/couch.js ("(function (doc) {var count = 0;for (var idx in doc._attachments) {co 79: test/javascript/tests/attachment_views.js () 37: test/javascript/cli_runner.js runTest() 48: test/javascript/cli_runner.js [31mfail ``` Sample couch.log content: ``` [info] 2017-05-30T19:36:00.862817Z [email protected] <0.2237.0> -------- Starting index update for db: shards/a0000000-bfffffff/test_suite_db_rsaxbqjx.1496172960 idx: _design/temp_dhrvvuyu [error] 2017-05-30T19:36:00.903666Z [email protected] <0.2202.0> -------- OS Process Error <0.2117.0> :: {os_process_error,{exit_status,139}} [info] 2017-05-30T19:36:00.903800Z [email protected] <0.222.0> -------- couch_proc_manager <0.2117.0> died normal [error] 2017-05-30T19:36:00.903990Z [email protected] <0.2148.0> a631af55fb rexi_server throw:{os_process_error,{exit_status,139}} [{couch_mrview_util,get_view,4,[{file,"src/couch_mrview_util.erl"},{line,52}]},{couch_mrview,query_view,6,[{file,"src/couch_mrview.erl"},{line,244}]},{rexi_server,init_p,3,[{file,"src/rexi_server.erl"},{line,139}]}] [error] 2017-05-30T19:36:00.904339Z [email protected] <0.1724.0> a631af55fb req_err(2090670111) os_process_error : {exit_status,139} [<<"couch_mrview_util:get_view/4 L52">>,<<"couch_mrview:query_view/6 L244">>,<<"rexi_server:init_p/3 L139">>] ``` ## Possible Solution There was a comment on IRC about this: ```irc 14:02 < vatamane> I had built a centos 7 vagrant vm before but couldn't reproduce 14:02 < vatamane> however i encountered segfaults in couchjs when was playing with changing its max heap parameter, -S I think 14:03 < vatamane> the segfault was triggered by garbage collection 14:35 <+jan____> eeenteresting 14:35 <+jan____> we dropped support for this between 1.x and 2.x and only fixed it after 2.0, which means, I think, that Cloudant never ran that code 14:41 <+jan____> ?and subsequently didn?t see any potential segfaults 14:42 < vatamane> the idea there at some point was that making the max heap big enough just delayed the garbage collection indefinitely ``` This is a recurrence of JIRA issue COUCHDB-3352. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
