wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-311858916
Two runs done with no segfaults. I'm declaring victory for now - we would
have had a segfault by now.
Again, please reopen this ticket if another
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-311832165
One run done so far with no segfaults (though 4 other errors).
This is an automated message
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-311813243
Images are still uploading; once they have I'll push the button on Jenkins
to run a few times and will share results in this ticket. If it's not fixed,
I'll
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-311736726
Lunch gave me some perspective. I'm proceeding with a 3-step approach:
1. Compile js-1.8.5 from source in all Docker images, with the
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-311714266
So we've been talking this over on #couchdb-dev IRC.
The working theory is:
```
jit + fortify source + extra stack protection causes
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-311714266
So we've been talking this over on #couchdb-dev IRC.
The working theory is:
```
jit + fortify source + extra stack protection causes
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-307992413
So to me this suggests it's not a strict memory leak that's failing. Your
idea from IRC about capturing all the stdio for the couchjs process and using
that
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-306934907
Based on @nickva 's suppositions, I attempted a low-memory, low-stack-size
invocation of couch and couchjs respectively. For reference:
```sh
$
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-306934907
Based on @nickva 's suppositions, I attempted a low-memory, low-stack-size
invocation of couch and couchjs respectively. For reference:
```sh
$
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-306934907
Based on @nickva 's suppositions, I attempted a low-memory, low-stack-size
invocation of couch and couchjs respectively. For reference:
```sh
$
wohali commented on issue #551: [Jenkins] couchjs segfaults
URL: https://github.com/apache/couchdb/issues/551#issuecomment-306934907
Based on @nickva 's suppositions, I attempted a low-memory, low-stack-size
invocation of couch and couchjs respectively. For reference:
```sh
$
11 matches
Mail list logo
