After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 85525 - Lockup caused by clicking on main window while writing followup
Lockup caused by clicking on main window while writing followup
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.12.0 betas
Other Linux
: Normal normal
: 0.13.0
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-06-17 00:51 UTC by Carl Hudkins
Modified: 2006-06-18 05:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Runlog of activity leading up to lockup (4.62 KB, application/octet-stream)
2002-06-17 00:54 UTC, Carl Hudkins
Details
Finally caught it... here's the backtrace! (20.71 KB, text/plain)
2002-06-25 02:04 UTC, Carl Hudkins
Details

Description Carl Hudkins 2002-06-17 00:51:43 UTC
Procedure:
Read article containing first part of multi-part binary.
<F> to followup.
Click on main window.
==> Pan consumes 100% CPU and is unresponsive to stimuli.

No tasks running; Pan is otherwise idle.
Comment 1 Carl Hudkins 2002-06-17 00:54:03 UTC
Created attachment 9264 [details]
Runlog of activity leading up to lockup
Comment 2 Charles Kerr 2002-06-17 04:35:08 UTC
I can't reproduce this bug, but the trace is pretty good.
I'll look into this for 0.12.1.

(BTW please just attach them as .txt files so that they're
easier to read in a browser.)
Comment 3 Carl Hudkins 2002-06-25 02:04:00 UTC
Created attachment 9441 [details]
Finally caught it... here's the backtrace!
Comment 4 Carl Hudkins 2002-06-25 02:06:52 UTC
Durnit... don't know what happened with the browser, but that 
attachment is *not* for this problem, it's for segfault-on-exit... 
please remove it if you can!  :(
Sorry...
Comment 5 Charles Kerr 2002-07-19 17:50:07 UTC
The end of that runlog:

(                        text.c:0293:             
update_body_pane)(thread 0x814b7e0)(time 00:38:05)(depth   4) TRACE: +
update_body_pane^M
(                        text.c:0224:    
append_text_buffer_nolock)(thread 0x814b7e0)(time 00:38:05)(depth   5)
TRACE: + append_text_buffer_nolock
(                        text.c:0285:    
append_text_buffer_nolock)(thread 0x814b7e0)(time 00:38:05)(depth   4)
TRACE: - append_text_buffer_nolock
(                        text.c:0300:             
update_body_pane)(thread 0x814b7e0)(time 00:38:05)(depth   3) TRACE: -
update_body_pane
(            identity-manager.c:0236: 
identity_manager_get_default)(thread 0x814b7e0)(time 00:38:05)(depth 
 4) TRACE: + identity_manager_get_default
(            identity-manager.c:0183:
identity_manager_get_identity)(thread 0x814b7e0)(time 00:38:05)(depth
  5) TRACE: + identity_manager_get_identity
(            identity-manager.c:0199:
identity_manager_get_identity)(thread 0x814b7e0)(time 00:38:05)(depth
  4) TRACE: - identity_manager_get_identity
(            identity-manager.c:0245: 
identity_manager_get_default)(thread 0x814b7e0)(time 00:38:05)(depth 
 3) TRACE: - identity_manager_get_default
(           
identity-manager.c:0292:identity_manager_get_identities)(thread
0x814b7e0)(time 00:38:05)(depth   4) TRACE: +
identity_manager_get_identities
(           
identity-manager.c:0302:identity_manager_get_identities)(thread
0x814b7e0)(time 00:38:05)(depth   3) TRACE: -
identity_manager_get_identities
(            identity-manager.c:0183:
identity_manager_get_identity)(thread 0x814b7e0)(time 00:38:05)(depth
  4) TRACE: + identity_manager_get_identity
(            identity-manager.c:0199:
identity_manager_get_identity)(thread 0x814b7e0)(time 00:38:05)(depth
  3) TRACE: - identity_manager_get_identity
(                        text.c:0293:             
update_body_pane)(thread 0x814b7e0)(time 00:38:05)(depth   4) TRACE: +
update_body_pane
(                        text.c:0224:    
append_text_buffer_nolock)(thread 0x814b7e0)(time 00:38:05)(depth   5)
TRACE: + append_text_buffer_nolock
(                        text.c:0285:    
append_text_buffer_nolock)(thread 0x814b7e0)(time 00:38:05)(depth   4)
TRACE: - append_text_buffer_nolock
(                        text.c:0300:             
update_body_pane)(thread 0x814b7e0)(time 00:38:05)(depth   3) TRACE: -
update_body_pane
(                       group.c:0998:         
group_unref_articles)(thread 0x814b7e0)(time 00:38:05)(depth   4)
TRACE: + group_unref_articles
(                       group.c:1039:         
group_unref_articles)(thread 0x814b7e0)(time 00:38:05)(depth   3)
TRACE: - group_unref_articles
(                         gui.c:0218:           
gui_set_title_idle)(thread 0x814b7e0)(time 00:38:05)(depth   4) TRACE:
+ gui_set_title_idle
(                
articlelist.c:0288:articlelist_get_selected_count_nolock)(thread
0x814b7e0)(time 00:38:05)(depth   5) TRACE: +
articlelist_get_selected_count_nolock
(                
articlelist.c:0292:articlelist_get_selected_count_nolock)(thread
0x814b7e0)(time 00:38:05)(depth   4) TRACE: -
articlelist_get_selected_count_nolock
(                         gui.c:0250:           
gui_set_title_idle)(thread 0x814b7e0)(time 00:38:05)(depth   3) TRACE:
- gui_set_title_idle

(pan:26074): Gtk-CRITICAL **: file ../../gtk/gtktextiter.c: line 3525
(gtk_text_iter_set_line_offset): assertion `char_on_line <=
chars_in_line' failed
(                       queue.c:1160:               
sockets_upkeep)(thread 0x81a1500)(time 00:38:20)(depth   1) TRACE: +
socket_upkeep
(                       queue.c:1245:               
sockets_upkeep)(thread 0x81a1500)(time 00:38:20)(depth   0) TRACE: -
socket_upkeep
Comment 6 Charles Kerr 2002-07-31 15:50:11 UTC
0.12 branch is probably complete, so bumping these
for investigation in 0.13.1
Comment 7 Charles Kerr 2002-08-04 00:16:59 UTC
I can't duplicate this in cvs head (soon to be 0.12.93).

Carl, I think this is fixed.  I suspect it was caused by the
way Pan handled reading a single part of a multipart binary
in 0.12.0, which has been cleaned up a great deal.

Please re-open if you can still tickle the problem, but based
the way the code has changed between 0.11.94 and 0.12.93 I'm
going to go out on a limb and mark this closed.