Re: [alpine-aports] phantonjs question
First off, thank you for the reply. Second, sorry it took so long
to get back to you.
I’ve compiled PhantomJS in several different ways, and I keep
getting a hangup on even trivial examples. I’ve opened a bug here:
I was able to reproduce the same hangup in an image built from your
Dockerfile. So far I’m not seeing anything interesting in strace,
for now I seem to be stuck. I’ll keep digging, but curious if you can
> On Apr 8, 2016, at 1:36 AM, Natanael Copa <ncopa_at_alpinelinux.org> wrote:
> On Thu, 7 Apr 2016 21:50:43 -0500
> Nathan Johnson <nathan_at_nathanjohnson.org> wrote:
>> I*m playing with a phantomjs port, and it looks like Natanael Copa
>> already made two PRs to some deps to make it compile (Thanks Natanael!).
>> I can*t help but think he*s already started down this path.
>> The bad news is, the test harness seems to bomb. If I run this under
>> the grsec kernel, it signal 11*s all over the place. If I run under
>> vanilla, no segfaults, but it does time out when phantomjs tries to
>> connect to the python httpd process. For what it*s worth, I also get
>> similar timeouts when doing a wget to localhost on the same port, so
>> I am inclined to believe it might be an issue with the python script.
> phantomjs uses JIT which does not work with the memory protections in
> grsec kernel. You have to disable those for the phantomjs binary:
> paxctl -cm bin/phantomjs
>> If I don*t hear anything back, I*ll continue into the rabbit hole.
>> Just wanted to make sure I wasn't duplicating effort.
> I published the Dockerfile I used to build phantomjs:
> Unsubscribe: alpine-aports+unsubscribe_at_lists.alpinelinux.org
> Help: alpine-aports+help_at_lists.alpinelinux.org
Received on Sun Apr 10 2016 - 09:42:49 GMT