Greg Steuck <[email protected]> writes:

> On Tue, Aug 18, 2020 at 10:50 PM Robert Nagy <[email protected]> wrote:
>
>  What is your fd limit? Please monitor fstat and see which process goes out 
> of whack with file descriptor usage.
>
> Presumably we verify that the minimal viable value of 400 is available, I have
> % ulimit -Sn
> 512
>  
> I'll keep an eye on fstat now that I got up to chromium-84.0.4147.125. As of 
> now I'm at:
> % fstat | grep chrome | sort -k4 -n | tail -n3
> greg     chrome     19291  263 /home     7405655  -rw-------    rp    81109
> greg     chrome     19291  264 /home     6340676  -rw-------    wp       41
> greg     chrome     19291  265 /home     6340678  -rw-------    wp   277820

I just caught it in the act. The problem happened immediately
after I opened a new tab and clicked on a bookmark. The last messages
on the terminal were:
[776:1999349824:0825/151540.925317:ERROR:broker_posix.cc(46)] Received 
unexpected number of handles
[12040:1600703552:0825/154243.105441:ERROR:batching_media_log.cc(38)] 
MediaEvent: 
{"error":"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
 
name\":\"DecryptingVideoDecoder\"},\"stack\":[],\"status_code\":265,\"status_message\":\"\"}"}
[12040:1600703552:0825/154243.105567:ERROR:batching_media_log.cc(38)] 
MediaEvent: 
{"error":"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[],\"status_code\":265,\"status_message\":\"\"}],\"data\":{\"Decoder
 
name\":\"VpxVideoDecoder\"},\"stack\":[],\"status_code\":265,\"status_message\":\"\"}"}
[12040:1600703552:0825/154243.105662:ERROR:batching_media_log.cc(38)] 
MediaEvent: 
{"error":"{\"causes\":[{\"causes\":[],\"data\":{\"codec\":\"h264\"},\"stack\":[],\"status_code\":260,\"status_message\":\"\"}],\"data\":{\"Decoder
 
name\":\"Dav1dVideoDecoder\"},\"stack\":[],\"status_code\":265,\"status_message\":\"\"}"}
[22261:-1543819200:0825/154243.141976:ERROR:bus.cc(393)] Failed to connect to 
the bus: Could not parse server address: Unknown address type (examples of 
valid types are "tcp" and on UNIX "unix")
[22261:-1543819200:0825/154243.142274:ERROR:bus.cc(393)] Failed to connect to 
the bus: Could not parse server address: Unknown address type (examples of 
valid types are "tcp" and on UNIX "unix")
[22261:-1543819200:0825/154243.142396:ERROR:bus.cc(393)] Failed to connect to 
the bus: Could not parse server address: Unknown address type (examples of 
valid types are "tcp" and on UNIX "unix")
[22261:-181162896:0825/165355.245720:ERROR:CONSOLE(0)] "Error with 
Feature-Policy header: Unrecognized feature: 'notifications'.", source:  (0)
[22261:-181162896:0825/165355.246014:ERROR:CONSOLE(0)] "Error with 
Feature-Policy header: Unrecognized feature: 'push'.", source:  (0)
[22261:-181162896:0825/165355.246123:ERROR:CONSOLE(0)] "Error with 
Feature-Policy header: Unrecognized feature: 'speaker'.", source:  (0)
[22261:-181162896:0825/165355.246398:ERROR:CONSOLE(0)] "Error with 
Feature-Policy header: Unrecognized feature: 'vibrate'.", source:  (0)
[22261:-616195520:0825/200454.120839:ERROR:socket_stream.cc(219)] Closing 
stream with result -2
[84559:1953532480:0825/200507.757431:ERROR:broker_posix.cc(43)] Invalid node 
channel message
[1]    22261 trace trap (core dumped)  chrome

The fstat loop indeed shows a spike of FD consumption:
% while fstat | grep chrome | sort -n -k4 | tail -n4; do sleep 3; done
...
greg     chrome     22261  260 /home     3793682  -rw-------    wp    33278
greg     chrome     22261  262 /home     3793749  -rw-------    rp    96311
greg     chrome     22261  266 /home     3796762  -rw-------  rwep    28672
greg     chrome     22261  281 /home     3793814  -rw-------    rp    41095
greg     chrome     22261  260 /home     3793682  -rw-------    wp    33278
greg     chrome     22261  262 /home     3793749  -rw-------    rp    96311
greg     chrome     22261  266 /home     3796762  -rw-------  rwep    28672
greg     chrome     22261  281 /home     3793814  -rw-------    rp    41095
greg     chrome     22261  260 /home     3793682  -rw-------    wp    33278
greg     chrome     22261  262 /home     3793749  -rw-------    rp    96311
greg     chrome     22261  266 /home     3796762  -rw-------  rwep    28672
greg     chrome     22261  281 /home     3793814  -rw-------    rp    41095
greg     chrome     22261  260 /home     3793682  -rw-------    wp    33278
greg     chrome     22261  262 /home     3793749  -rw-------    rp    96311
greg     chrome     22261  266 /home     3796762  -rw-------  rwep    28672
greg     chrome     22261  281 /home     3793814  -rw-------    rp    41095
greg     chrome     22261  507 /home     9354833  -rw-------   rwp     1016
greg     chrome     22261  508 /home     9354790  -rw-------   rwp     1025
greg     chrome     22261  509 /home     9354856  -rw-------   rwp     1094
greg     chrome     22261  511 /tmp           41* -rw-------   rwp       80

The steady state of < 300 seems stable in normal regime. I'll up the
limit to 600 and see if I can still hit the problem.

Thanks
Greg

Reply via email to