Don't receive messages after getting display picture

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run WLM and log in with one account (contact A). Make sure a display
picture is set. I'm using 14.0.8089.726
2. Run the sample client and log in on another account (contact B).
3. In the sample client, double click on contact A to open a conversation
window. Wait until the contact A's display picture is transferred and
displayed.
4. In WLM, double click on contact B and send a text message.

What is the expected output? What do you see instead?
The message sent from WLM should be displayed in the sample client.
Instead, no message is displayed.

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
MSNPSharp 3.0.1 on Windows XP SP2, .net 2.0

Please provide any additional information below:
WLM seems to send the message via DirectIM P2P once the P2P switchboard is
opened. This is parsed just fine, but in
SBMessageHandler.OnTextMessageReceived(), TextMessageReceived is null for
the P2P switchboard, and so no event is raised.

After the display picture is transferred, this switchboard remains alive,
even after the conversation is ended.

It also doesn't happen every time, but I can reproduce it pretty consistently. 

Original issue reported on code.google.com by dllexp...@gmail.com on 2 Dec 2009 at 1:48

[GoogleCodeExporter]

We can't reproduce this problem.

Original comment by freezing...@gmail.com on 3 Dec 2009 at 9:00

• Changed state: Invalid

[GoogleCodeExporter]

Please see the attached screenshot of the problem after it occurs. I can also 
send
you a memory dump of the process if you like. The problem is quite real.

Original comment by dllexp...@gmail.com on 4 Dec 2009 at 3:44

Attachments:

• scrn.png

[GoogleCodeExporter]

Would you please check out the latest code from the SVN and test again?

Original comment by freezing...@gmail.com on 4 Dec 2009 at 4:47

[GoogleCodeExporter]

Original comment by freezing...@gmail.com on 4 Dec 2009 at 4:48

• Changed state: New

[GoogleCodeExporter]

Problem occurs in revision 1440 of the MSNPSHARP_30_STABLE branch. Trace looks 
the
same too:

----
P2PHandler: Parsing incoming msg message
SBMessagePool: Buffering data...: 
SBMessagePool: MessageAvailable: SBMessageProcessor: Message received:
MSG dllexport@hotmail.com Andy 125
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-MMS-IM-Format: FN=Verdana; EF=; CO=800080; CS=0; PF=22

fdfdf

SBMessageProcessor: Handling received message MSNPSharp.SBMessageHandler 
SessionHash:
746450138.7455253.84170112
SBMessageProcessor: Handling received message MSNPSharp.DataTransfer.P2PHandler
P2PHandler: Parsing incoming msg message
NSMessageProcessor: Outgoing message:
PNG

NSMessageProcessor: Parsing incoming NS command...
----

It is strange that you cannot reproduce this issue. Maybe try using accounts 
other
than the sample client test account?

Original comment by dllexp...@gmail.com on 4 Dec 2009 at 5:13

[GoogleCodeExporter]

If you still cannot reproduce this problem, I can set it up on one of my 
machines
with Visual Studio and let you remote in to debug.

Original comment by dllexp...@gmail.com on 5 Dec 2009 at 5:16

[GoogleCodeExporter]

I think you should clean the project and build again, I've tried many times, 
still 
cannot reproduce it.

Original comment by freezing...@gmail.com on 5 Dec 2009 at 6:26

[GoogleCodeExporter]

I did clean the project just now. Same problem.

Could you try this please: after step 4), close the sample client's chat window 
and
then close the chat window in WLM. Open a chat window to the sample client in 
WLM and
send a message.

This triggers the bug as well (no msg is received). It occurs much more 
reliably than
if you don't close the chat windows.

Perhaps you want to try with my account: dllexport@gmail.com, password is 
pasward
I tried it just now, and I can receive the message sometimes if I don't close 
the
chat windows. But if I do close them, I cannot receive messages anymore.

Original comment by dllexp...@gmail.com on 5 Dec 2009 at 6:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This might be a regression... I can get it to work properly in v3.0.0 
sometimes, but
not other times.

Original comment by dllexp...@gmail.com on 6 Dec 2009 at 3:19

[GoogleCodeExporter]

I successfully reproduce it, please wait for the fix.

Original comment by freezing...@gmail.com on 7 Dec 2009 at 6:56

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r1458.

Original comment by freezing...@gmail.com on 20 Jan 2010 at 9:06

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by freezing...@gmail.com on 21 Jan 2010 at 8:03

• Added labels: Milestone-Release3.1.0