#23751: [warn] tor_bug_occurred_: Bug: src/common/buffers.c, etc. ------------------------------------------------+-------------------------- Reporter: Felixix | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Tor: | 0.3.2.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-channel, tor-sched, tor-buffer | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------------------------+--------------------------
Comment (by pastly): Here's some thoughts. - Isn't the outbuf limited to like 32KB in size? - If the scheduler was what filled up the outbuf, would Vanilla done the same thing? Why or why not? Does Vanilla check a limit that KIST/KISTLite doesn't? Since Vanilla doesn't write outbuf->kernel, wouldn't it be __more__ likely to hit this? - What was the state of the channel that got a full outbuf? Was it closing? Was data continuing to pour in and for some reason we were never able to write, and thus the outbuf filled up? How many scheduling rounds did it take for this to happen? Did it all happen in one? Bah. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23751#comment:3> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs