From: sup-talk@gurski.org (Michael Gurski)
Subject: [sup-talk] crash while sup is sitting idle
Date: Fri, 28 Mar 2008 23:03:56 -0400 [thread overview]
Message-ID: <20080329030356.GA8459@gurski.org> (raw)
After a 28+ hour sup-sync -a -o, on git head, sup sitting idle crashed
with the following error:
--- Ferret::StateError from thread: load threads for thread-index-mode
State Error occured at <except.c>:93 in xraise
Error occured in index.c:4150 - sr_get_lazy_doc
Document 69 has already been deleted
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:421:in `[]'
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:421:in `[]'
/usr/lib/ruby/1.8/monitor.rb:238:in `synchronize'
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:413:in `[]'
./lib/sup/index.rb:228:in `each_id_by_date'
./lib/sup/index.rb:228:in `each'
./lib/sup/index.rb:228:in `each_id_by_date'
./lib/sup/thread.rb:326:in `load_n_threads'
./lib/sup/modes/thread-index-mode.rb:507:in
`__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
./lib/sup/modes/thread-index-mode.rb:491:in
`load_n_threads_background'
./lib/sup.rb:60:in `reporting_thread'
./lib/sup.rb:58:in `initialize'
./lib/sup.rb:58:in `new'
./lib/sup.rb:58:in `reporting_thread'
./lib/sup/modes/thread-index-mode.rb:490:in
`load_n_threads_background'
./lib/sup/modes/thread-index-mode.rb:560:in
`__unprotected_load_threads'
(eval):12:in `load_threads'
./lib/sup/modes/thread-index-mode.rb:70:in `initialize'
./lib/sup/modes/line-cursor-mode.rb:177:in `call'
./lib/sup/modes/line-cursor-mode.rb:177:in `call_load_more_callbacks'
./lib/sup/modes/line-cursor-mode.rb:177:in `each'
./lib/sup/modes/line-cursor-mode.rb:177:in `call_load_more_callbacks'
./lib/sup/modes/line-cursor-mode.rb:80:in `cursor_down'
./lib/sup/mode.rb:49:in `send'
./lib/sup/mode.rb:49:in `handle_input'
./lib/sup/buffer.rb:231:in `handle_input'
bin/sup:223
--- SystemExit from thread: main
State Error occured at <except.c>:93 in xraise
Error occured in index.c:4150 - sr_get_lazy_doc
Document 69 has already been deleted
./lib/sup.rb:64:in `select'
./lib/sup/buffer.rb:31:in `nonblocking_getch'
bin/sup:217
--
Michael A. Gurski (opt. [first].)[last]@pobox.com http://www.pobox.com/~[last]
1024R/39B5BADD PGP: 34 93 A9 94 B1 59 48 B7 17 57 1E 4E 62 56 45 70
1024D/1166213E GPG: 628F 37A4 62AF 1475 45DB AD81 ADC9 E606 1166 213E
4096R/C0B4F04B GPG: 5B3E 75D7 43CF CF34 4042 7788 1DCE B5EE C0B4 F04B
Views expressed by the host do not reflect the staff, management or sponsors.
next reply other threads:[~2008-03-29 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 3:03 Michael Gurski [this message]
2008-04-01 15:35 ` William Morgan
2008-04-01 16:52 ` Michael Gurski
2008-04-01 17:13 ` William Morgan
2008-04-01 19:50 ` Michael Gurski
2008-04-01 20:03 ` Christopher Warrington
2008-04-03 1:43 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080329030356.GA8459@gurski.org \
--to=sup-talk@gurski.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox