Bug #978
Twitter engine fails retrieving timelines after some time with Object reference not set to an instance of an object
Status: | New | Start: | 08/12/2014 | |
Priority: | Urgent | Due date: | ||
Assigned to: | Mirco Bauer | % Done: | 0% |
|
Category: | Engine Twitter | |||
Target version: | 0.11.1 | |||
Complexity: | Found in Version: | 0.11 on Archlinux (AUR PGK) |
||
Votes: | 0 |
Description
Steps to reproduce¶
- Add a new Twitter account
- Authorize it (with /pin xxxxxxx)
- Take a beer
Expected behavior¶
All three default timelines (Home, answers and DM) should stay in the left column and remain accessible.
Current behavior¶
After some time (I presume during the first sync after successful auth) the home and DM timeline disapear. The server log show this stack trace:
2014-08-12 10:38:27,198 [TwitterProtocolManager friends timeline listener] ERROR Smuxi.Engine.TwitterProtocolManager - UpdateFriendsTimelineThread(): Exception System.NullReferenceException: Object reference not set to an instance of an object at System.Net.ServicePoint.SendRequest (System.Net.HttpWebRequest request, System.String groupName) [0x00072] in /build/mono/src/mono-3.4.0/mcs/class/System/System.Net/ServicePoint.cs:430 at System.Net.HttpWebRequest.GetResponseAsyncCB2 (System.Net.WebAsyncResult aread) [0x00094] in /build/mono/src/mono-3.4.0/mcs/class/System/System.Net/HttpWebRequest.cs:964 at System.Net.HttpWebRequest.BeginGetResponse (System.AsyncCallback callback, System.Object state) [0x000e8] in /build/mono/src/mono-3.4.0/mcs/class/System/System.Net/HttpWebRequest.cs:917 at System.Net.HttpWebRequest.GetResponse () [0x00000] in /build/mono/src/mono-3.4.0/mcs/class/System/System.NetHttpWebRequest.cs:1000 at Twitterizer.WebRequestBuilder.ExecuteRequest () [0x00009] in /build/smuxi/src/smuxi-0.11/lib/Twitterizer/Twitterizer2/OAuth/WebRequestBuilder.cs:244 at Twitterizer.Core.TwitterCommand`1[Twitterizer.TwitterStatusCollection].ExecuteCommand () [0x00275] in /build/smuxi/src/smuxi-0.11/lib/Twitterizer/Twitterizer2/Core/TwitterCommand.cs:191 at Twitterizer.Core.CommandPerformer.PerformAction[TwitterStatusCollection] (ICommand`1 command) [0x00008] in /build/smuxi/src/smuxi-0.11/lib/Twitterizer/Twitterizer2/Core/CommandPerformer.cs:51 at Twitterizer.TwitterTimeline.HomeTimeline (Twitterizer.OAuthTokens tokens, Twitterizer.TimelineOptions options) [0x0000a] in /build/smuxi/src/smuxi-0.11/lib/Twitterizer/Twitterizer2/Methods/Timeline/TwitterTimeline.cs:54 at Smuxi.Engine.TwitterProtocolManager.UpdateFriendsTimeline () [0x00000] in <filename unknown>:0 at Smuxi.Engine.TwitterProtocolManager.UpdateFriendsTimelineThread () [0x00000] in <filename unknown>:0
Complementary info¶
After the exception occurs, a second twitter account appears in the server manage window (same username, same options). Don't know if it could be linked or not.
History
Updated by Mirco Bauer 3737 days ago
Can you provide a debug log? Start smuxi-frontend-gnome from a terminal with -d and paste the last 10-20 lines from the output. Right now it sounds like it could be a bug in Mono but that is a wild guess.
Updated by Étienne Deparis 3737 days ago
I'll add it ASAP. For now I resolved my problem by manually editing the file ~/.config/smuxi/smuxi-engine.ini and removing all unnecessary entries. Thus to provide the log file I must delete my profile and start over to reproduces the bug. I'll do this before the end of the week.
Updated by Étienne Deparis 3735 days ago
- File smux_server added
- File smux_log added
Here it is.
I've started a fresh smuxi-server session and just after smuxi-frontend-gnome in debug mode. Here are the two complete log file. I stopped the watch after the second twitter engine crash. Hope you have enough data with that.