Hmm, this might be a problem unique to the EPEL packages. We are stuck on
Pygments 1.4 while ReviewBoard recommends 1.6+ IIRC. I may have to look at
packaging an alternate version for use with RB.
On Tue, Jul 11, 2017 at 11:46 PM Alexey Neyman <alexey.ney...@gmail.com>
wrote:

> Hi,
>
> We've seen a rather odd behavior of RB today. Once a certain text was
> inserted inside "verbatim" markdown block (four backticks before and
> after), the Apache process running ReviewBoard became a CPU hog, consuming
> 100% of CPU time. Interestingly, the "Description" displayed the text fine,
> but no email notification has been sent.
>
> The offending text is in the attached file (1.txt). A colleague suggested
> to send SIGABRT to that Apache process, which yielded the the stacktrace in
> the Apache's logs, also attached as stacktrace.txt
>
> ReviewBoard and Pygments both installed from RPMs:
>
> ReviewBoard-2.5.7-1.el7.noarch
> python-pygments-1.4-9.el7.noarch
>
> Regards,
> Alexey.
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to