nickva commented on issue #551: [Jenkins] couchjs segfaults URL: https://github.com/apache/couchdb/issues/551#issuecomment-307954410 I looked at this a bit today. Compiled couchjs from mozjs 1.8.5 source on a CentOS 7 VM. The created a patch to run log all couchjs inputs to file. Then fed that input to that couchjs process in a loop. So far no crashes. The ran valgrind against couchjs with a few lines of input. It found a whole bunch of uninitialized variable uses but apparently those are ok according to upstream and to reduce the noise have to set `./configure --enable-valgrind` that made it better and only showed two leaks: ``` ==2212== ==2212== HEAP SUMMARY: ==2212== in use at exit: 608 bytes in 2 blocks ==2212== total heap usage: 1,157,666 allocs, 1,157,664 frees, 470,097,237 bytes allocated ==2212== ==2212== 40 bytes in 1 blocks are definitely lost in loss record 1 of 2 ==2212== at 0x4C27BE3: malloc (vg_replace_malloc.c:299) ==2212== by 0x4056EF: couch_parse_args (util.c:75) ==2212== by 0x4048E2: main (main.c:388) ==2212== ==2212== 568 bytes in 1 blocks are still reachable in loss record 2 of 2 ==2212== at 0x4C27BE3: malloc (vg_replace_malloc.c:299) ==2212== by 0x596654C: __fopen_internal (iofopen.c:73) ==2212== by 0x405529: slurp_file (util.c:36) ==2212== by 0x405CDA: couch_readfile (util.c:203) ==2212== by 0x404B53: main (main.c:449) ==2212== ==2212== LEAK SUMMARY: ==2212== definitely lost: 40 bytes in 1 blocks ==2212== indirectly lost: 0 bytes in 0 blocks ==2212== possibly lost: 0 bytes in 0 blocks ==2212== still reachable: 568 bytes in 1 blocks ==2212== suppressed: 0 bytes in 0 blocks ==2212== ==2212== For counts of detected and suppressed errors, rerun with: -v ==2212== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ``` Those are ok. It would be good to clean them up but the process exits at that point it doesn't seem like the culprit. ---------------------------------------------------------------- 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
