Closed herrhotzenplotz closed 1 week ago
Hi @herrhotzenplotz, thanks for the report, i also noticed it a while ago, this bug will be closed by https://github.com/contour-terminal/contour/pull/1497 once it is merged
@herrhotzenplotz the linked PR sadly cannot be merged too soon, because it's actually removing some optimization path. But until it is fixed for real, we are working on a temporary workaround.
One question: Do you actively use the statusline feature? Was it enabled during the time you have been hitting the crash?
EDIT: p.s.: looking at your backtrace, looks like the statusline was enabled. You can avoid it by making sure it is disabled (when pumping out a lot of output) - until it's fixed. :)
EDIT/2: we've both looked into the source code again, looks like we can actually use this PR. Sorry for the confusion. :)
One question: Do you actively use the statusline feature? Was it enabled during the time you have been hitting the crash?
No I don't - in fact I find it kinda irritating (prolly because I am not used to it). And yes, it was enabled during the crash.
EDIT/2: we've both looked into the source code again, looks like we can actually use this PR. Sorry for the confusion. :)
Great stuff!
I am getting assertion failures again when dumping a lot of output (e.g. running
find /
)Possibly another case of the solution to #1444
Debugger backtrace: