From: Ben Walton <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue99] persistent crash with "wrong id called on nil"
Date: Thu, 06 May 2010 14:14:49 +0000 [thread overview]
Message-ID: <1273155288.81.0.0378934243374.issue99@masanjin.net> (raw)
In-Reply-To: <1273155288.81.0.0378934243374.issue99@masanjin.net>
New submission from Ben Walton <bwalton@artsci.utoronto.ca>:
This one is driving me nuts. I'm not able to determine which message
(threadset) causes it yet. Sometimes I can run for a few minutes, view
messages, etc. The next time, sup crashes almost immediately after startup.
This started with a crash last night (random after running for days). I
couldn't get sup to restart. I ended up hosing my index...I've now rebuilt it
and while I can run sup again, the crashes continue.
Ideas? This is going to be long day...
Thanks
-Ben
--- RuntimeError from thread: load threads for thread-index-mode
wrong id called on nil
./sup.rb:17:in `id'
./sup/modes/thread-index-mode.rb:234:in `update'
./sup/hook.rb:123:in `sort_by'
./sup/modes/thread-index-mode.rb:234:in `each'
./sup/modes/thread-index-mode.rb:234:in `sort_by'
./sup/modes/thread-index-mode.rb:234:in `update'
./sup/modes/thread-index-mode.rb:232:in `synchronize'
./sup/modes/thread-index-mode.rb:232:in `update'
./sup/modes/thread-index-mode.rb:652:in `__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
./sup/modes/thread-index-mode.rb:624:in `load_n_threads_background'
./sup.rb:77:in `reporting_thread'
./sup.rb:75:in `initialize'
./sup.rb:75:in `new'
./sup.rb:75:in `reporting_thread'
./sup/modes/thread-index-mode.rb:623:in `load_n_threads_background'
./sup/modes/thread-index-mode.rb:694:in `__unprotected_load_threads'
(eval):12:in `load_threads'
./sup/modes/thread-index-mode.rb:89:in `initialize'
./sup/modes/line-cursor-mode.rb:22:in `call'
./sup/modes/line-cursor-mode.rb:22:in `initialize'
./sup/modes/line-cursor-mode.rb:22:in `each'
./sup/modes/line-cursor-mode.rb:22:in `initialize'
./sup/modes/line-cursor-mode.rb:19:in `new'
./sup/modes/line-cursor-mode.rb:19:in `initialize'
./sup/modes/thread-index-mode.rb:60:in `initialize'
./sup/modes/inbox-mode.rb:14:in `initialize'
../bin/sup:193:in `new'
../bin/sup:193
----------
messages: 223
nosy: bwalton
priority: bug
ruby_version: 1.8.5
status: unread
sup_version: next
title: persistent crash with "wrong id called on nil"
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue99>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2010-05-06 14:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1273155288.81.0.0378934243374.issue99@masanjin.net>]
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=1273155288.81.0.0378934243374.issue99@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@rubyforge.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