Bug 231541 - www/lynx: always starts with zombie process
Summary: www/lynx: always starts with zombie process
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
Depends on:
Reported: 2018-09-21 12:01 UTC by Marco Beishuizen
Modified: 2021-02-22 18:28 UTC (History)
2 users (show)

See Also:
jharris: maintainer-feedback-


Note You need to log in before you can comment on or make changes to this bug.
Description Marco Beishuizen 2018-09-21 12:01:58 UTC
Starting lynx (from ports, version 2.8.9) always starts with two processes: one "normal" working process and one child zombie process.

Rebuilding didn't help.

Uname -a: FreeBSD yokozuna 11.2-STABLE FreeBSD 11.2-STABLE #0 r335773: Fri Jun 29 15:55:48 CEST 2018     root@yokozuna:/usr/obj/usr/src/sys/YOKOZUNA  amd64

Comment 1 Alex Kozlov freebsd_committer freebsd_triage 2018-09-29 09:53:00 UTC
I can't reproduce this. Can you please provide more details?
Comment 2 Marco Beishuizen 2018-09-29 10:21:47 UTC
I don't know if I can tell much more. These are the lynx processes in htop after start: 

66549 marco      20   0 23364  8884 S  0.0  0.2  0:03.57    │  │        ├─ xterm -geometry 110x40 -title lynx
66550 marco      20   0 16180 10480 S  0.0  0.3  0:00.77    │  │        │  └─ lynx
67187 marco      21   0     0     0 Z  0.0  0.0  0:00.01    │  │        │     └─ lynx
Comment 3 Alex Kozlov freebsd_committer freebsd_triage 2018-09-29 11:23:08 UTC
I guess you're starting lynx through xterm: xterm -e lynx ... , so this is not lynx but xterm's bug. I still can't reproduce this zombie lynx, though.
Comment 4 Marco Beishuizen 2018-09-29 12:25:50 UTC
I'm not sure. It also happens when starting lynx in urxvt and it didn't happen in the previous version

But it isn't a big problem either, lynx runs fine.
Comment 5 Alex Kozlov freebsd_committer freebsd_triage 2018-09-29 12:58:35 UTC
Hmm. I've compared code between 2-8-8rel2 and 2.8.9rel1. There are some changes in WWW/Library/Implementation/HTTCP.c (the only place where lynx uses fork). Can you please:
1) Start xterm/rxvt, run lynx in it manually and see if you still can reproduce this zombie issue.
2) Remove --enable-nsl-fork from CONFIGURE_ARGS in port's Makefile, rebuild port and try to reproduce lynx's zombie.
Comment 6 Marco Beishuizen 2018-09-29 14:25:44 UTC
Yes removing the "--enable-nsl-fork" in the Makefile did the trick. Zombie is gone.

Comment 7 jharris 2019-06-13 19:02:28 UTC
(In reply to Marco Beishuizen from comment #6)

Based on this result, do we still need to keep this bug open?

Comment 8 Marco Beishuizen 2019-06-15 12:08:52 UTC
Not sure. The solution is more of a workaround. I can make a patch to make "--enable-nsl-fork" optional?
Comment 9 Alex Kozlov freebsd_committer freebsd_triage 2019-06-17 21:50:51 UTC
It's easy to add such option, but I don't see much reason to do that. The zombie should disappear after exiting parent lynx, so this situation is harmless.