Re: 4/4 CVS Build - Huge Jump in Responsiveness - Just ME?

[Gene ENonymous <yancm@xxxxxxxxxxxxxxxx>]

Hey Roger,

Just a quick update...

When I recompile w/out pthreads, I get a different error, repeated alot
of times:

Apr 04 16:49:44.442 [notice] Tor 0.1.0.2-rc-cvs opening log file.
Apr 04 17:42:32.956 [warn] connection_unregister(): Error removing write
event for 56
Apr 04 17:42:32.958 [warn] connection_unregister(): Error removing read
event for 61
Apr 04 17:42:32.958 [warn] connection_unregister(): Error removing write
event for 61
  [snip about 50 like this]
Apr 04 17:42:33.940 [warn] connection_unregister(): Error removing write
event for 97
Apr 04 19:38:28.364 [warn] connection_unregister(): Error removing read
event for 60
  [snip about 75 more...]
Apr 04 19:38:29.098 [warn] connection_unregister(): Error removing write
event for 126
clarity 196 ->   date
Mon Apr  4 19:47:25 EST 2005

tor won't die with a normal kill. It takes a kill -9.

I have recompiled with pthreads and cvs update...now it just dies
outright kinda like it has been since Thursday on and off.

****Update report ****
CVS build, sync'd at 7:50PM EST on 4/4
Warning file:
Apr 04 19:59:21.484 [err] Catching signal TERM, exiting cleanly.
Apr 04 19:59:23.653 [notice] Tor 0.1.0.2-rc-cvs opening log file.
Apr 04 20:14:04.569 [err] dnsworker_main(): writing answer failed. Child
exiting.
Apr 04 20:27:30.656 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:27:30.656 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:28:02.746 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:28:02.747 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:31:10.581 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:31:10.581 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:31:10.581 [warn] purge_expired_resolves(): Bug: Expiring a dns
resolve that's still pending. Forgot to cull it?
Apr 04 20:39:08.591 [warn] connection_dns_process_inbuf(): Bug: read data
from an idle dns worker.  Please report.
Apr 04 20:41:05.930 [err] dns.c:645: connection_dns_process_inbuf:
Assertion buf_datalen(conn->inbuf) == 5 failed; aborting.

gdb backtrace:
(gdb) bt
#0  0x48221feb in kill () from /usr/lib/libc.so.12
#1  0x48296a3f in abort () from /usr/lib/libc.so.12
#2  0x0806be69 in connection_dns_process_inbuf (conn=0x82f8700) at dns.c:664
#3  0x0805ad3c in connection_handle_read (conn=0x82f8700) at connection.c:954
#4  0x08071576 in conn_read_callback (fd=54, event=2, _conn=0x82f8700)
    at main.c:358
#5  0x481f2a8c in event_process_active () from /usr/lib/libevent.so.0
#6  0x481f2c35 in event_loop () from /usr/lib/libevent.so.0
#7  0x481f2ab6 in event_dispatch () from /usr/lib/libevent.so.0
#8  0x08071f7d in do_main_loop () at main.c:949
#9  0x0807151d in tor_main (argc=6, argv=0xbfbffba4) at main.c:1588
#10 0x0808327b in main (argc=6, argv=0xbfbffba4) at tor_main.c:19
#11 0x0804bb22 in ___start ()

I'll take pthread support out again...it will take a little while to
compile and run...I'll post what I find later.

Point of order...should I keep posting this to the or-talk list or should
I open a bug track item? (if so, suggestions on what to call it? "Crashes
in current 4/4?")

Thanks,
gene

-----------------------------------------------------------------

On Mon, April 4, 2005 4:29 pm, Roger Dingledine said:
> On Mon, Apr 04, 2005 at 03:10:27PM -0500, Gene ENonymous wrote:
>> Apr 04 08:34:53.583 [warn] purge_expired_resolves(): Bug: Expiring a dns
>> resolve that's still pending. Forgot to cull it?
>
> Hi Gene,
>
> This is an interesting bug. Has anybody else been seeing it?
[snip]
> One possibility is that it could be pthread bugs on netbsd. Could you
> comment out the "#define HAVE_PTHREAD_CREATE 1" line in orconfig.h,
> recompile, and see whether it continues to happen?