On Mon, Jul 10, 2017 at 08:48:11PM +0000, Ryan Mulligan <[email protected]> wrote:
> I got this backtrace:
Thanks, that's a lot more useful!
> Program received signal SIGSEGV, Segmentation fault.
> rxvt_term::scr_alloc (this=this@entry=0x722040) at screen.C:193
> 193 l.t = (text_t *)base; base += tsize;
Now, what happens here is that urxvt allocates a big memory block for the
terminal data (including the scorllback/saveLines area) and then creates
an array of line_t structures inside. I'd say chances of a bug here are
very low.
My guess would be that you simply ran out of memory, causing urxvt to
crash - one could argue that it didn't give a nice diagnostic, but in the
end, if there isn't enough memory, the only thing it can do is crash in
some way (especially since it might happen on a memory access).
You cna try
p chunk
when you get that SEGV, to see if chunk is zero. if it is, then thsi is
the case, if it isn't, you might sitll run out of memory, but diagnosing
will be harder.
> This problem seems intermittent, because VirtualBox froze on me and when I
Chances are the Virtualbox (or the VM?) froze on you because it, too, ran
out of memory.
That it happens on maximize would be a good indicator as well, as that's
when it has to allocate the largest amount of memory.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
