Hi,
On Fri, Nov 11, 2011 at 12:56:04PM +0200, Timo Juhani Lindfors wrote:
Upstream maintainer said got GC Warning but no SEGV.
Maybe it depends on how much memory you have? I had only 128 MB at that
time I think.
I have 2G memory. I think w3m does not considere so low memory,
so I am
d+...@vdr.jp writes:
I have 2G memory. I think w3m does not considere so low memory,
so I am afraid that it will not fix. If you need fix absolutely,
I will forward it again.
128 MB is all the memory that my openmoko phone has. But don't worry,
I've already switched to lighter browsers like
d+...@vdr.jp writes:
Upstream maintainer said got GC Warning but no SEGV.
Maybe it depends on how much memory you have? I had only 128 MB at that
time I think.
-Timo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
[ Sorry for the late reply, I never got your email that asked for more
info. Please remember to use 415132-submit...@bugs.debian.org if you
want me to get the emails.]
Seems that today w3m just gets killed by the out of memory
killer. (And amazingly it also causes so much swapping that the
tags 415132 + moreinfo
thanks
I cannot reproduce this problem.
I use w3m 0.5.2-9, libgc1c2 1:7.1-3 and 1:6.8-1.2.
I do not get GC Warning and no SEGV.
Upstream maintainer says get GC Warning but no SEGV.
If this problem still exists,
please show dependency libraries version, especially libgc.
Package: w3m
Version: 0.5.1-5.1
Severity: normal
Steps to reproduce:
1) w3m -dump http://iki.fi/lindi/w3m-htmlgen-1180.html /dev/null
Expected results:
1) w3m renders web page to /dev/null and exits
Actual results:
1) w3m prints
GC Warning: Out of Memory! Returning NIL!
Segmentation fault
6 matches
Mail list logo
