Description of problem: I think I just hit 'r' to reply to a message. But, was stands out is that a few commands eariler, I tried to open a URL that was huge and my web-browser never loaded the page. Normally, that works fine. But, I've noticed this before with very long URLs. Version-Release number of selected component: alpine-2.10-4.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 crash_function: fs_give executable: /usr/bin/alpine kernel: 3.11.4-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 13013 Truncated backtrace: Thread no. 1 (10 frames) #5 fs_give at fs_unix.c:68 #6 free_color_table at color.c:1072 #7 pico_toggle_color at color.c:1231 #8 pico_endcolor at color.c:1272 #9 end_screen at termout.unx.c:333 #10 ttyfix at signal.c:737 #11 pipe_callback at signal.c:563 #12 open_system_pipe at pipe.c:336 #13 dfilter at dispfilt.c:102 #14 detach at detach.c:315
Created attachment 824997 [details] File: backtrace
Created attachment 824998 [details] File: cgroup
Created attachment 824999 [details] File: core_backtrace
Created attachment 825000 [details] File: dso_list
Created attachment 825001 [details] File: environ
Created attachment 825002 [details] File: limits
Created attachment 825003 [details] File: maps
Created attachment 825004 [details] File: open_fds
Created attachment 825005 [details] File: proc_pid_status
Created attachment 825006 [details] File: var_log_messages
Hi, I couldn't reproduce the crash with a the following huge URL: http://www.thelongestlistofthelongeststuffatthelongestdomainnameatlonglast.com/wearejustdoingthistobestupidnowsincethiscangoonforeverandeverandeverbutitstilllookskindaneatinthebrowsereventhoughitsabigwasteoftimeandenergyandhasnorealpointbutwehadtodoitanyways.html Does that crash for you? Can you attach your .pinerc (feel free to remove usernames etc)
Nope, that's way to short. I consistently have problems from this one site that sends me appointment reminders and the URL is takes up six lines. Unfortunately, I don't have any e-mails from them right now. I'll probably receive a new one soon-ish, though. Perhaps that was a red herring, anyway. The crash didn't happen until a few commands after I tried to open that particular URL. Was the crash not helpful?
Created attachment 826330 [details] .pinerc
*** This bug has been marked as a duplicate of bug 914999 ***
Joshua, This bug is not a duplicate of bug 914999. I still do not understand it completely but Bug 914999 is a crash during string conversion between charsets. The data is not complete. Paul, when reporting bugs obfuscating information is not a good idea, because the obfuscated information might be the culprit of the crash. Please do not do so in the future. This bug has to do with the fact that color support is not thread safe, so there are two ways to make this problem go away that do not involve patching Alpine. One is to disable thread support at the configure stage, and the other turn colors off. The harder thing to do is to modify Alpine to make color support thread safe. This is not trivial. Color support is so pervasive in Alpine that modifying this takes several days. I made some progress on this during last summer, and might work on it again later, bit do not hold your breath for it. Just to be clear, this bug has nothing to do with URL length. Paul, my hunch is that if you disable color support that you will not be able to repeat this crash.
Hi Eduadro, Interesting. Thanks so much for digging so deep. I understand what you are saying. I think I'll just live with it; it's infrequent enough that I'd rather have the colors. I'll not report this in the future if the backtrace includes color stuff. Josh, Maybe you should leave this as ASSIGNED or CLOSED ERRATA, just for posterity, since it's not really a dup.
Sure, done