The same box experienced an out of memory (4GB!) event (or two) and tor got killed, and restarted. Nothing much else is running there which is quiet stable.

Trac:
Username: udo

MaxMemInQueues 1024 MB

So OoM is unexpected.

Trac:
Username: udo

In fact OoM events happen multiple times per day. They did not before this. Is this due to some open ports? Or solely because of this version?

Trac:
Username: udo

I closed all open ports to see if that 'fixes' the issue (makes it not appear anymore). I.e.: relay-only for now.

Trac:
Username: udo

So far tor appears to be more stable. No OoM and no assertion events.

Trac:
Username: udo

With just port 22 and 53 open the issue does not happen. (yet)

Trac:
Username: udo

Even with just port 22 and 53 open I do get OoM events. Please provide a fix soon!

Trac:
Username: udo

If the reason is not found before, can you please try if this also happens with the 0.3.3.x series and 0.3.4.7. Is it reproducible with other ports?

Add the 035-must tag to some assertion failures, hangs, ci-blockers, etc.

Trac:
Keywords: N/A deleted, 035-must added

Mark all 035-must tickets as "very high"

Trac:
Priority: Medium to Very High

It would be very very helpful to know what's the first version that shows this issue.

Trac:
Owner: N/A to dgoulet
Status: new to accepted

note: dgoulet and I are going to try to have a look here.

I think this could be related to the token bucket changes in #25373 (moved).

This may be fixed by the fix of #28089 (moved); let's see whether it recurs in 0.3.5.3-alpha or later. (Or in 0.3.4.9 or later.)

Trac:
Status: accepted to needs_information

tor-0.3.3.9-0.fc28.x86_64 does NOT have this issue.

While trying to build an rpm for 0.3.5.3.-alpha I try: Version: 0.3.5.3-%{alphatag} but:

rpmbuild -bb SPECS/tor.spec

error: line 23: Illegal char '-' (0x2d) in: Version: 0.3.5.3-alpha

I.e.: one cannot have a dash ('-') there when building rpm. but I do need to tell rpm the exact version string as it also expects this version in the directory tree in the source tar file.

Trac:
Username: udo

After 0.3.3.9 I went to 0.3.4.8 which has the issue.

Trac:
Username: udo

Now running 0.3.5.3-alpha. We will need a few days to be fairly sure.

Trac:
Username: udo