abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html -dump /mnt/compartido/asolis/Skeletor.htm.htm component: w3m executable: /usr/bin/w3m kernel: 2.6.32.9-70.fc12.i686 package: w3m-0.5.2-15.fc12 rating: 4 reason: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 401671 [details] File: backtrace
What is this Skeletor.htm.htm page? Can you also attach it? I think problem should be releated to this page only.
w3m is used and called by the Tracker (indexer program). [apons@atlantis asolis]$ file Skeletor.htm.htm Skeletor.htm.htm: Non-ISO extended-ASCII text, with very long lines, with no line terminators Skeletor.htm.htm size is 18 Mbytes. The Skeletor.htm.htm file has private contents and I not allowed to send it.
I think you need to reduce it to a smaller testcase: try to work out if it is triggered one of the command-line options, or what part of your file is causing the crash. I also recommend reporting the issue to upstream since they are much more familiar with the code-base.
Also might be worth testing earlier versions of w3m if you think this is a regression.
I tried to reproduce the error in command line but I did not succeed. Even if I obtained the following warnings: [root@atlantis apons]# w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html -dump /tmp/Skeletor.htm.htm GC Warning: Repeated allocation of very large block (appr. size 8716288): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26746880): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26746880): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26746880): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26578944): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26578944): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26578944): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26554368): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26550272): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26550272): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26550272): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26550272): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26546176): May lead to memory leak and poor performance. GC Warning: Repeated allocation of very large block (appr. size 26546176): May lead to memory leak and poor performance.
Are you still able to reproduce this?
No, sorry. I do not happened again.
I will close this now then. If again crashes report it in bz. Thanks.