Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 3930 by Garbage collection and registered signals cause errors during cron job execution of index and session cleanup tasks

*** You must complete this form in its entirety, or your bug report will be
*** rejected.
*** If you have a security issue to report, please send it confidentially
*** Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
*** For customer support, please post to
*** If you have a patch, please submit it to
*** This bug tracker is public. Please check that any logs or other
*** that you include has been stripped of confidential information.

What version are you running?
2.5 beta2

What's the URL of the page containing the problem?

CRON tasks as defined in conf/cron.conf

What steps will reproduce the problem?

1.Use the provided cron jobs via crontab as per
2. Execute cron task
3. Observe STDERR output

What is the expected output? What do you see instead?

Task completes, but generates STDERR output which shows an error:

Exception TypeError: TypeError('isinstance() arg 2 must be a class, type, or tuple of classes and types',) in <bound method Signal._remove_receiver of <django.dispatch.dispatcher.Signal object at 0x7f9b106be750>> ignored

Assuming if root issue can't be resolved, this exception should be trapped and logged so as to not create misleading CRON task reports / errors?

What operating system are you using? What browser?

Ubuntu Server 14.04 / Google Chrome (not applicable)

Please provide any additional information below.

See existing forum thread at:!msg/reviewboard/Mv4Y183SAVM/lcg--dl16RUJ

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to