Witty 0.1.5 crashing often on Vista

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run Witty 0.1.5

Often Witty crashes.  I think it may be tied some how to getting Twitter 
updates.  When twitter is down it seems to happen more regularly making me 
thing it has to do with exception handling when Twitter responds back with 
erractic or no information.

I can get some logs/traces when I get more time.

Original issue reported on code.google.com by kurtbroc...@gmail.com on 16 Nov 2007 at 6:10

[GoogleCodeExporter]

Below is the Crash Dialog from my Windows Vista Ultimate machine 32-bit.
Not sure if there is any relevant information but I am still seeing constant 
crashing.

----------------------------------------------------------------

Description:
  Stopped working

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: witty.exe
  Problem Signature 02: 0.1.5.30595
  Problem Signature 03: 4744d486
  Problem Signature 04: PresentationFramework
  Problem Signature 05: 3.0.0.0
  Problem Signature 06: 453054bb
  Problem Signature 07: 6496
  Problem Signature 08: be
  Problem Signature 09: System.Windows.Markup.XamlParse
  OS Version:   6.0.6000.2.0.0.256.1
  Locale ID:    1033

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Original comment by kurtbroc...@gmail.com on 8 Dec 2007 at 6:36

[GoogleCodeExporter]

I am also experiencing these random, but semi regular crashes. 

I have to force kill to get the application to go away, most frustrating 
because it's
such a great twitter client. :)

Original comment by bhabe...@gmail.com on 10 Dec 2007 at 12:15

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Guys I receive similar crashes and have pulled down the source.  It'd seem that 
at least in my case it happens in the UpdateUserInterface method at this point: 

tweets[i].UpdateRelativeTime();

The unhandled exception thrown is ArgumentOutOfRangeException - copied the 
callstack 
below.  I've wrapped the call in an if the following way in order to get past 
this 
from a short-term perspective but should look into it further.  In no way do I 
suggest this as a long-term fix as I don't understand the symptom (perhaps 
Twitter 
downs etc): i'd need to look further into the control flow.

if (tweets.Count > i)
{
   tweets[i].UpdateRelativeTime();
}

Heads-up, 

Matt Ortiz | email: matt[at]footheory[dot]com | twitter: @mortiz

--------------

Exception: 

System.ArgumentOutOfRangeException occurred    Message="Index was out of range. 
Must 
be non-negative and less than the size of the collection.\r\nParameter name: 
index"    Source="mscorlib"    ParamName="index"    StackTrace:         at 
System.ThrowHelper.ThrowArgumentOutOfRangeException()         at 
System.Collections.Generic.List`1.get_Item(Int32 index)         at 
System.Collections.ObjectModel.Collection`1.get_Item(Int32 index)         at 
Witty.MainWindow.UpdateUserInterface(TweetCollection newTweets) in 
..\Witty\MainWindow.xaml.cs:line 242    InnerException:   

Original comment by ma77or...@gmail.com on 4 Jan 2008 at 7:22

[GoogleCodeExporter]

Here are some VSTest methods that simulate the issue: 

Matt Ortiz | email: matt[at]footheory[dot]com | twitter: @mortiz

--------------

Tests: 

        [TestMethod]
        [ExpectedException(typeof(ArgumentOutOfRangeException))]
        public void ArgumentOutOfRange_IsolatedRepro()
        {
            TweetCollection tweets = new TweetCollection();
            Tweet tweet = new Tweet();
            tweet.Text = "testing index out of range";
            tweets.Add(tweet);
            tweets[1].UpdateRelativeTime();
        }

        [TestMethod]
        public void ArgumentOutOfRange_IsolatedRepro_ShortTermFix()
        {
            TweetCollection tweets = new TweetCollection();
            Tweet tweet = new Tweet();
            tweet.Text = "testing index out of range";
            tweets.Add(tweet);
            int i = 1;
            if (tweets.Count > i)
            {
                tweets[i].UpdateRelativeTime();
            }
        }

Original comment by ma77or...@gmail.com on 4 Jan 2008 at 7:27

[GoogleCodeExporter]

Thanks guys. I applied a path by Omar that fixes the index out of range problem.
Please let me know if this is still an issue.

Original comment by alan...@gmail.com on 7 Feb 2008 at 6:04

• Changed state: Fixed