Github user oknet commented on the issue:
https://github.com/apache/trafficserver/issues/1401
@zwoop @bryancall
I think we can close this issue since #1522 and #1559 have merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1401
epoll_wait trigger EVENTIO_ERROR(in read or write) would case segfault,
because we do not set any state in vc(by calling do_io_xxx). we just recevie
sockets and register in epoll_wait.
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1401
epoll_wait triggered EVENTIO_ERROR after accept(do_blocking_accept) will
cause coredump, because we do not call any do_io_xx. In 6.x.x we do not handle
EVENTIO_ERROR eventï¼it may cause vc
Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/issues/1401
Finally get a use-after-free ASAN stack in this area. Anyone else having
problems with ASAN in newer builds?
Looks like it is showing a use after free in the case of the error
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/issues/1401
I'm not sure there is a core to look at in the case I pasted. It was on a
build host.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/issues/1401
BTW I'm currently testing without HTTP/2.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/issues/1401
@PSUdaemon would be cool to see symbols with the stack to verify that is
the same thing. My hacky fix made it go away only to be immediately replaced
by a new crash. (New issue to be
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/issues/1401
I think I am [seeing
this](https://ci.trafficserver.apache.org/job/ubuntu_14_04-6.2.x/compiler=clang,label=ubuntu_14_04,type=release/143/console)
in 6.2.x as well:
```
Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/issues/1401
I've finally got my environment running and I see the same stack very
quickly as well. In the cases I've seen it looks like there was a write error,
but for some reason the write vio has
Github user bryancall commented on the issue:
https://github.com/apache/trafficserver/issues/1401
(gdb) bt full
#0 0x005150b0 in Mutex_trylock (m=0x0, t=0x2b44f3a6d010)
at
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1401
Are you getting a core file / backtrace ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user biilmann commented on the issue:
https://github.com/apache/trafficserver/issues/1401
Not this one no. We've seen a crash that looks related in the crash logs
from 7.0.x but it is much rarer and I don't currently have a core-dump of that.
---
If your project is set up for
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1401
you didn't see this crasher in 7.0.0 right ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user biilmann commented on the issue:
https://github.com/apache/trafficserver/issues/1401
Some info on the vc:
```
p vc
$1 = (UnixNetVConnection *) 0x2b9a7802ff10
p vc.closed
$2 = 0
p vc.action_
$3 = {_vptr.Action = 0x788a90 , continuation =
Github user bryancall commented on the issue:
https://github.com/apache/trafficserver/issues/1401
What does the vc look like?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user biilmann opened an issue:
https://github.com/apache/trafficserver/issues/1401
Segfault in write_to_net_io with 7.1.x
Seeing frequent segfaults when trying 7.1.x on some production traffic.
What happens is that the `MUTEX_TRY_LOCK_FOR` segfaults since
16 matches
Mail list logo
