Created attachment 483109 [details] GDB backtraces for pidgin Description of problem: I was typing a message to an offline friend of mine when pidgin suddenly froze. This happened multiple times, but only when using a specific font and window size. Version-Release number of selected component (if applicable): pidgin-2.7.10-1.fc14.x86_64.rpm pango-1.28.1-4.fc14.x86_64.rpm How reproducible: Every time for this very specific setup Steps to Reproduce: 1. Log in to GNOME 2. Go to System -> Preferences -> Appearance 2a. Select the Fedora theme 2b. Select the following fonts: Sans 10, Sans 10, Sans 10, Sans Bold 10, Monospace 10 and Subpixel smoothing (LCDs) 3. Create the following symlinks: - /etc/fonts/conf.d/10-autohint.conf -> /etc/fonts/conf.avail/10-autohint.conf - /etc/fonts/conf.d/10-sub-pixel-rgb.conf -> /etc/fonts/conf.avail/10-sub-pixel-rgb.conf 4. Double check font settings: [ciupicri@hermes ~]$ fc-match Sans DejaVuSans.ttf: "DejaVu Sans" "Book" 5. Start pidgin and login to a Yahoo account. It might work with other protocols as well, but I haven't tested this. 6. Start a conversation with an offline buddy, although I don't think this matters; it worked once with an online buddy, too. 7. Before typing anything, resize the window to something close to 587 x 473 pixels. You could even start with a width of 600 pixels. The screenruler package might be useful for this. 8. Type the message "aiastppl eut http://www.facebook.com/in.cuurraanadi#!/photo.php?fbid=069710401708640&set=a.553584074287109.56943.063020100808195&theater " 9. If pidgin doesn't freeze resize the window very slowly and make it narrower until pidgin freezes. Actual results: Pidgin freezes Expected results: Pidgin shouldn't freeze Additional info: elb from #pidgin thinks that this might be related to pango. Another interesting bug is #673830. I wasn't able to reproduce the bug with a wider window (627 x 544) or with the Droid fonts from Google.
Created attachment 483112 [details] Screenshot: pidgin freezes
Created attachment 483113 [details] Screenshot: pidgin works fine
Created attachment 483114 [details] /var/log/rpmpkgs
Created attachment 483115 [details] GDB backtraces for pidgin backtrace; cont; wait a couple of seconds; backtrace; cont; ...
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
pidgin-2.10.5-1.fc17.x86_64 seems to work fine.
Created attachment 641855 [details] GDB backtraces for pidgin
pidgin froze when I pasted some text in a window. I'm using pidgin-2.10.5-1.fc17.x86_64 and pango-1.30.0-1.fc17.x86_64.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Does this issue still persist on even f19 say?
I haven't upgraded to Fedora 19 yet, but if I remember correctly it happened to me once on Fedora 18. Anyway, I've tried to reproduce it again right now, but I either had no luck or the software is working as it should. If it happens again I'll reopen this bug.
Sure. thanks for the comment. I'll close this so far against it. please reopen when you see this again.
Still happening with pidgin-2.13.0-15.fc31.x86_64 & pango-1.44.7-1.fc31.x86_64 but I don't know an easy way to reproduce it. It seems to be happen when I write longer messages which require at least two lines.
Could someone provide one simple pango test case with C code to reproduce this bug? I think that test case can help debugging the pango code.
Still happening with pidgin-2.13.0-17.fc32.x86_64 & pango-1.44.7-2.fc32.x86_64.
Could you open new bug for pidgin? Then we can discuss with pidgin maintainers.
Why a new one instead of just adding them to the CC list? Also keep in mind that it's very hard to reproduce the bug. It happens to me only a couple of times per year.
I think the code has changed since the bug report. Please attach updated backtrace and update the reproduce steps. It will be helpful to have another bug for pidgin to fix this issue.
Maybe I have same. Pidgin freezes sometimes consuming 100% of one CPU core. How to reproduce: paste specific URL to chat (don't need to send). Reproducibility: rarely for all URLs; 100% for specific URL. URL example which causes freeze: https://touch.facebook.com/story.php?story_fbid=2552013635069508&id=1418070198463863&refid=52&_ft_=qid.6806424231271081512%3Amf_story_key.-1743871993554616785%3Atop_level_post_id.2552013635069508%3Acontent_owner_id_new.1418070198463863%3Apage_id.1418070198463863%3Asrc.22%3Aphoto_id.2552008885069983%3Astory_location.5%3Astory_attachment_style.photo%3Aview_time.1584657524%3Afilter.h_nor%3Atds_flgs.3%3Apage_insights.%7B%221418070198463863%22%3A%7B%22page_id%22%3A1418070198463863%2C%22actor_id%22%3A1418070198463863%2C%22dm%22%3A%7B%22isShare%22%3A0%2C%22originalPostOwnerID%22%3A0%7D%2C%22psn%22%3A%22EntStatusCreationStory%22%2C%22post_context%22%3A%7B%22object_fbtype%22%3A266%2C%22publish_time%22%3A1584552253%2C%22story_name%22%3A%22EntStatusCreationStory%22%2C%22story_fbid%22%3A%5B2552013635069508%5D%7D%2C%22role%22%3A1%2C%22sl%22%3A5%2C%22targets%22%3A%5B%7B%22actor_id%22%3A1418070198463863%2C%22page_id%22%3A1418070198463863%2C%22post_id%22%3A2552013635069508%2C%22role%22%3A1%2C%22share_id%22%3A0%7D%5D%7D%7D&__tn__=-R SW versions: pidgin-2.13.0-15.fc31.x86_64 libpurple-2.13.0-15.fc31.x86_64 gtk2-2.24.32-6.fc31.x86_64 gtk3-3.24.13-1.fc31.x86_64 Below are several output samples of `ltrace -cfS -p $(pgrep pidgin) & sleep 10 ; kill %%` while freeze: # % time seconds usecs/call calls function ------ ----------- ----------- --------- -------------------- 66.53 13.547932 129 104440 restart_syscall 11.49 2.339960 118 19773 g_type_check_instance_cast 3.50 0.713426 469 1521 gtk_text_view_get_iter_location 1.79 0.364201 119 3042 gtk_text_view_get_type 1.74 0.354519 116 3042 gtk_text_view_get_line_yrange 1.09 0.221775 145 1521 gtk_object_get_type 1.04 0.211637 139 1521 gtk_text_buffer_get_line_count 0.94 0.190879 125 1521 gtk_text_view_get_buffer 0.91 0.186125 122 1521 gtk_text_buffer_get_end_iter 0.91 0.185201 121 1521 g_source_remove 0.90 0.183757 120 1521 gtk_text_iter_forward_line 0.90 0.183630 120 1521 g_idle_add_full 0.88 0.180046 118 1521 purple_prefs_get_int 0.88 0.179463 117 1521 gtk_text_view_get_visible_rect 0.88 0.179377 117 1521 gtk_text_view_get_pixels_above_lines 0.88 0.179313 117 1521 gtk_widget_style_get 0.87 0.176875 116 1521 gtk_text_view_get_pixels_below_lines 0.87 0.176228 115 1521 gtk_text_view_get_left_margin 0.86 0.175268 115 1521 gtk_text_view_get_pixels_inside_wrap 0.85 0.173669 114 1521 gtk_text_buffer_get_start_iter 0.85 0.173432 114 1520 gtk_text_view_get_right_margin 0.43 0.087026 114 760 gtk_widget_set_size_request ------ ----------- ----------- --------- -------------------- 100.00 20.363739 156913 total # % time seconds usecs/call calls function ------ ----------- ----------- --------- -------------------- 66.64 15.575763 124 124719 restart_syscall 11.58 2.705979 114 23614 g_type_check_instance_cast 3.36 0.785555 432 1817 gtk_text_view_get_iter_location 1.78 0.415542 114 3632 gtk_text_view_get_line_yrange 1.76 0.412049 113 3633 gtk_text_view_get_type 1.03 0.241876 133 1817 gtk_object_get_type 1.02 0.237638 130 1816 gtk_text_buffer_get_line_count 0.93 0.217082 119 1817 g_source_remove 0.91 0.212532 116 1817 g_idle_add_full 0.91 0.212044 116 1816 gtk_widget_style_get 0.90 0.211217 116 1817 purple_prefs_get_int 0.90 0.209760 115 1816 gtk_text_iter_forward_line 0.88 0.205997 113 1817 gtk_text_view_get_pixels_above_lines 0.88 0.205802 113 1817 gtk_text_view_get_buffer 0.87 0.204426 112 1816 gtk_text_buffer_get_end_iter 0.87 0.204102 112 1816 gtk_text_view_get_left_margin 0.87 0.203045 111 1817 gtk_text_view_get_pixels_inside_wrap 0.87 0.202724 111 1816 gtk_text_view_get_right_margin 0.87 0.202397 111 1816 gtk_text_view_get_visible_rect 0.86 0.201723 111 1817 gtk_text_view_get_pixels_below_lines 0.86 0.200857 110 1817 gtk_text_buffer_get_start_iter 0.45 0.105396 116 908 gtk_widget_set_size_request ------ ----------- ----------- --------- -------------------- 100.00 23.373506 187388 total # % time seconds usecs/call calls function ------ ----------- ----------- --------- -------------------- 66.53 15.520432 126 122923 restart_syscall 11.59 2.704793 116 23296 g_type_check_instance_cast 3.36 0.782825 436 1792 gtk_text_view_get_iter_location 1.79 0.418522 116 3584 gtk_text_view_get_line_yrange 1.76 0.410923 114 3584 gtk_text_view_get_type 1.05 0.245361 136 1792 gtk_object_get_type 1.03 0.239677 133 1792 gtk_text_buffer_get_line_count 0.97 0.225197 125 1792 g_source_remove 0.93 0.216015 120 1792 gtk_widget_style_get 0.93 0.215829 120 1792 g_idle_add_full 0.91 0.212984 118 1792 gtk_text_iter_forward_line 0.90 0.211020 117 1792 purple_prefs_get_int 0.88 0.204806 114 1792 gtk_text_view_get_left_margin 0.87 0.203331 113 1792 gtk_text_view_get_pixels_below_lines 0.87 0.203211 113 1792 gtk_text_buffer_get_end_iter 0.87 0.202224 112 1792 gtk_text_view_get_visible_rect 0.87 0.201923 112 1792 gtk_text_view_get_buffer 0.86 0.201593 112 1792 gtk_text_buffer_get_start_iter 0.86 0.201244 112 1792 gtk_text_view_get_pixels_above_lines 0.86 0.201171 112 1792 gtk_text_view_get_pixels_inside_wrap 0.86 0.199634 111 1792 gtk_text_view_get_right_margin 0.45 0.105213 117 896 gtk_widget_set_size_request 0.00 0.000099 24 4 brk ------ ----------- ----------- --------- -------------------- 100.00 23.328027 184751 total # % time seconds usecs/call calls function ------ ----------- ----------- --------- -------------------- 66.27 15.531356 131 118269 restart_syscall 11.68 2.736112 122 22415 g_type_check_instance_cast 3.41 0.798106 462 1724 gtk_text_view_get_iter_location 1.84 0.430221 124 3449 gtk_text_view_get_line_yrange 1.81 0.423686 122 3449 gtk_text_view_get_type 1.04 0.244677 141 1724 gtk_object_get_type 1.03 0.241033 139 1725 gtk_text_buffer_get_line_count 0.93 0.218319 126 1724 gtk_text_view_get_pixels_below_lines 0.93 0.217940 126 1724 g_idle_add_full 0.92 0.215042 124 1725 gtk_widget_style_get 0.92 0.214819 124 1725 gtk_text_iter_forward_line 0.90 0.211454 122 1724 g_source_remove 0.89 0.209008 121 1724 purple_prefs_get_int 0.89 0.207852 120 1724 gtk_text_view_get_right_margin 0.88 0.206991 119 1725 gtk_text_buffer_get_end_iter 0.88 0.206447 119 1725 gtk_text_view_get_visible_rect 0.88 0.206014 119 1724 gtk_text_buffer_get_start_iter 0.88 0.205441 119 1724 gtk_text_view_get_buffer 0.86 0.202053 117 1724 gtk_text_view_get_pixels_above_lines 0.86 0.201846 117 1724 gtk_text_view_get_pixels_inside_wrap 0.86 0.201414 116 1724 gtk_text_view_get_left_margin 0.45 0.105344 122 863 gtk_widget_set_size_request
> How to reproduce: paste specific URL to chat (don't need to send). Exactly, it's enough to type some text in the widget used for writing messages to be sent. And it seems to happen with text containing words too long for the widget, like there's a bug with the wrapping code.
Could you provide the gdb backtrace?
Created attachment 1672691 [details] five backtraces from gdb (In reply to Peng Wu from comment #22) > Could you provide the gdb backtrace? Is there a better way for it than hitting ctrl+c at random moments? Might be not accurate. Attaching 5 samples done like this.
Still present for pidgin-2.13.0-18.fc32.x86_64
Have it on pidgin-2.14.1-2.fc33.x86_64 as well (after F32 -> F33 upgrade)
Still present on F34: pidgin-2.14.1-3.fc34.x86_64
Shorter text to trigger this bug: algo_exp_id=90425218-a3ae-4612-8ea0-525d9ba6870d-47&pdp_ext_f=%7B%22sku_id%22%3A%2212000018382804572%22%7D Happens in facebook, hangouts and skype chats. Seems similar: bug #1953959
This bug can be reproduced in Fedora Xfce with "Sans 10" fonts.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Please update Fedora version here
It's still present on Fedora 35: pidgin-2.14.6-2.fc35.x86_64
It's still happening with pidgin-2.14.6-2.fc35.x86_64
It's still happening with pidgin-2.14.8-2.fc36.x86_64 and pango-1.50.7-1.fc36.x86_64
It's still happening with pidgin-2.14.8-4.fc36.x86_64 and pango-1.50.8-1.fc36.x86_64
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Does anyone still reproduce this issue in Fedora 38?
I don't remember having any issues under Fedora 38, but on the other hand this doesn't happen very often.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.