_curses.error: addstr() returned ERR #316
Comments
Thanks for the report |
It looks like http://bugs.python.org/issue8243. |
i wrapped the call to addstr in try: except: pass and did not notice anything wrong so far. If there is no better solution, we might just ignore the exception |
This error pops every time the program tries to draw text outside of the screen bounds. Usually it's the result of an edge case like resizing the screen in the middle of a redraw or trying to view an abnormal comment. I haven't seen one in a long time, so I'm surprised that you're getting them so frequently. What subreddits are you usually viewing when this happens? It could be a unicode character width miscalculation if you're on non-english subs. You can also try running with the ``--ascii` flag and see if that fixes the problem. |
Yes it looks like it is related to unicode, with --ascii i don't get these crashes. My unicode characters are horrible broken (I am just not sure, who is at fault, rtv or python) |
It sounds like your python build was compiled against the wrong curses library. I've seen similar jumbled characters like that when I built my own version of python. My understanding is that there are 2 versions of curses, libncurses.so and libncursesw.so, and the latter needs to be linked to python for unicode support. Here's a bug report that talks about the issue https://bugs.python.org/issue4787. What OS are you using? |
I added a section to the FAQ, but this seems like it's outside of the control of rtv so I'm closing the issue. |
Sometimes rtv terminates with the following exception,
I haven't really found a way to 100% reproduce this, but usually using rtv for 5-10 minutes results in one crash.
The text was updated successfully, but these errors were encountered: