Bug 254970

Summary: x11/terminology desktop environment becomes nearly unresponsive; problems involving devel/efl efreetd
Product: Ports & Packages Reporter: Graham Perrin <grahamperrin>
Component: Individual Port(s)Assignee: freebsd-enlightenment (Nobody) <enlightenment>
Status: Closed FIXED    
Severity: Affects Only Me CC: euan, peter
Priority: --- Flags: bugzilla: maintainer-feedback? (enlightenment)
Version: Latest   
Hardware: Any   
OS: Any   
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256408
Attachments:
Description Flags
tail of /var/log/messages none

Description Graham Perrin freebsd_committer freebsd_triage 2021-04-11 02:52:26 UTC 
I can't recall when I first installed Terminology (maybe years ago). I vaguely recall it being OK at the time. 

Today I tried maybe three times to use Terminology 1.9.0 with KDE Plasma on FreeBSD 14.0-CURRENT. On each occasion, shortly after performing a few actions the system became largely unresponsive for long periods. Almost no response to input on a peripheral USB keyboard; almost no response to trackball or trackpad input; and so on. htop in Konsole showed the kernel using around 300% CPU (4 CPUs). 

Actions such as: 

* using the scaler at start time

* clicking the grid button at top right

* resizing or moving the window

– nothing extraordinary. 

If I recall correctly: on the first occasion, Control-Alt-F2 eventually (after a long wait) got me to ttyv1 where I used htop to kill the process. 

In all cases: after killing or quitting Terminology, problems ceased. 

Below, the tail of /var/log/messages

----


Apr 11 02:39:39 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff80367363100 (local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 already in queue awaiting acceptance (1 occurrences)
Apr 11 02:41:05 mowa219-gjp4-8570p efreetd[75523]: stack overflow detected; terminated
Apr 11 02:41:06 mowa219-gjp4-8570p kernel: pid 75523 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Apr 11 02:41:07 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff80234076d00 (local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 already in queue awaiting acceptance (1 occurrences)
Apr 11 02:43:51 mowa219-gjp4-8570p login[1784]: ROOT LOGIN (root) ON ttyv1
Apr 11 02:44:07 mowa219-gjp4-8570p efreetd[75539]: stack overflow detected; terminated
Apr 11 02:44:07 mowa219-gjp4-8570p kernel: pid 75539 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Apr 11 02:44:35 mowa219-gjp4-8570p kernel: pid 75534 (urxvt), jid 0, uid 1002: exited on signal 10
Apr 11 02:50:53 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff803a151fc00 (local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 already in queue awaiting acceptance (1 occurrences)
Apr 11 02:51:35 mowa219-gjp4-8570p efreetd[75644]: stack overflow detected; terminated
Apr 11 02:51:36 mowa219-gjp4-8570p kernel: pid 75644 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Apr 11 02:52:22 mowa219-gjp4-8570p efreetd[75647]: stack overflow detected; terminated
Apr 11 02:53:43 mowa219-gjp4-8570p kernel: pid 75647 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Apr 11 02:54:42 mowa219-gjp4-8570p kernel: pid 75636 (urxvt), jid 0, uid 1002: exited on signal 10
Apr 11 03:01:23 mowa219-gjp4-8570p kernel: pid 75672 (urxvt), jid 0, uid 1002: exited on signal 10
Apr 11 03:01:30 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff80359509100 (local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 already in queue awaiting acceptance (1 occurrences)
Apr 11 03:02:16 mowa219-gjp4-8570p efreetd[75681]: stack overflow detected; terminated
Apr 11 03:02:17 mowa219-gjp4-8570p kernel: pid 75681 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Apr 11 03:03:53 mowa219-gjp4-8570p efreetd[75687]: stack overflow detected; terminated
Apr 11 03:04:24 mowa219-gjp4-8570p kernel: pid 75687 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Apr 11 03:05:46 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff802538eda00 (local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 already in queue awaiting acceptance (1 occurrences)
Apr 11 03:08:02 mowa219-gjp4-8570p efreetd[75691]: stack overflow detected; terminated
Apr 11 03:08:03 mowa219-gjp4-8570p kernel: pid 75691 (efreetd), jid 0, uid 1002: exited on signal 6 (core dumped)
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2021-04-11 02:55:05 UTC 
Created attachment 224007 [details]
tail of /var/log/messages

… sorry, I forgot that Bugzilla wraps long lines.
Comment 2 Peter TKATCHENKO 2021-04-11 10:13:24 UTC 
It seems that the problem is efreetd related - it crashes:
> stack overflow detected; terminated

Did you install EFL and Terminology from ports?
Did you used default EFL port setting?

We had many problems with efreetd in the past, but actually it seems to work correctly, I have no issues with it.

Could you, please, stop Terminology, stop all efreetd processes, then start Terminology from another terminal and paste here the output? Your environment variables could help to understand the issue too.
Comment 3 Euan Thoms 2021-06-04 12:36:47 UTC 
(In reply to Peter TKATCHENKO from comment #2)


This is most likely related to the recent bug report I just made which has a fix and is being dealt with by FreeBSD enlightenment team and upstream by the efl devs. I suspect the FD > 1024 was causing a lot of problems for a while on platforms that use the old select(2) system call for I/O multiplexing.

Refer to PR 256498.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256408
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2021-06-06 16:28:04 UTC 
Sorry for not responding sooner. 

Today, with the updated efl, Terminology seems fine, touch wood. 

root@mowa219-gjp4-8570p:~ # pkg info -x efl terminology
efl-1.25.1_9
terminology-1.9.0
root@mowa219-gjp4-8570p:~ #