Comment 1 by jteh on 2011-02-06 20:34
Can you be more specific about the crash? Please provide exact steps to reproduce, right from starting the program to where the crash occurs. Does it always happen or only intermittently?

Does it happen with NVDA 2010.2? if you're not sure, please test.

Can anyone else reproduce this?

Comment 2 by mdcurran on 2011-06-24 05:25
Old and no answer from reporter. Also in General Windows Live 2011 works ok for me. Please reopen if any more info can be provided.
Changes:
Added labels: worksforme
State: closed

Comment 3 by kara_louise (in reply to comment 2) on 2012-05-12 20:05
I can give more feedback on this as I'm experiencing a similar problem.
I'm using version 15.4.3538.0513 which at the time of writing is the latest version of windows live messenger.

To reproduce the problem, close a conversation window by pressing Escape. Windows Live Messenger will immediately crash then restart. It makes no difference if the main window is in standard or compact view, or if there's text in the conversation or not.

I'm using windows 7 with all the latest updates. Until I found this ticket, it seemed like I was the only one experiencing this problem so reproducing this may be difficult.
I'll be happy to provide more feedback if necissary.

Replying to mdcurran:

Old and no answer from reporter. Also in General Windows Live 2011 works ok for me. Please reopen if any more info can be provided.

Changes:
Removed labels: worksforme
State: reopened

Comment 4 by Brendon22 on 2012-05-12 23:22
Hi, Windows Live Messenger Version 15.4.3555.0308 does what is told in this ticket. And it is crashing using NVDA Version 2012.2beta1

Comment 5 by Brendon22 on 2012-05-14 09:19
Hi more information: Description
Faulting Application Path: C:\Program Files (x86)\Windows Live\Messenger\msnmsgr.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: msnmsgr.exe
Application Version: 15.4.3555.308
Application Timestamp: 4f596cbb
Fault Module Name: UXCore.dll
Fault Module Version: 15.4.3555.308
Fault Module Timestamp: 4f5960dc
Exception Code: c0000005
Exception Offset: 00110b55
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Extra information about the problem
Bucket ID: 2895735969

Comment 6 by Brendon22 on 2012-08-21 05:19
Hello,
NVDA is still crashing out in Windows Live Messager version 2011 Build 15.4.3538.0513, but interestingly though, I've just updated to Windows Live Messager Version 2012 Build 1643530728 and this crash doesn't happen. But there are still some problems: 1. NVDA will not read out who comes online. I have NVDA reading tool tips and Report help balloons checked and NVDA still doesn't read out this information to me?

1. The about NVDA window will not read out, the only way to access this information is by using the mouse keystrokes built into NVDA to get access to this informmation.
2. When you try and lode the program NVDA will not see that the program is there so you have To ault tabb away from the program and then ault tab back before NVDA will see that the program is there?

Comment 7 by Brendon22 on 2012-10-05 12:11
Hello,

What's happening with this ticket?

I still can't use Windows Live Messager it still crashes with NVDA?

Please can we have a fix with this ticket!

Comment 8 by mdcurran on 2012-10-08 23:44
I can reproduce the crash, but do not yet have an idea on how to fix it. As a temporary workaround, make sure you are not focused on the input field (by tabbing to another control in the chat window) before pressing alt+f4.

Technical info:
There is a crash somewhere in messenger's uxcore.dll, due to something to do with rpc, if you close a chat window while holding an ITextDocument pointer for the input field and then calling Release (i.e. Python deletes the object).

Changes:
Milestone changed from None to near-term

Comment 9 by kara_louise (in reply to comment 8) on 2012-10-09 00:23
Thanks very much for at least looking into it. :)
Replying to mdcurran:

I can reproduce the crash, but do not yet have an idea on how to fix it. As a temporary workaround, make sure you are not focused on the input field (by tabbing to another control in the chat window) before pressing alt+f4.

Technical info:

There is a crash somewhere in messenger's uxcore.dll, due to something to do with rpc, if you close a chat window while holding an ITextDocument pointer for the input field and then calling Release (i.e. Python deletes the object).

Comment 10 by Brendon22 on 2012-10-09 11:27
Hi Mic,
Thanks for that!

kara louise, another work around is to update to Windows Live 2012 Build 1643530728, that fixes this problem, but I still think that Windows Live 2011 should work as well!

Comment 11 by Brendon22 on 2013-06-09 03:15
Hi Mic,
Did you ever find out why uxcore.dll was crashing this program?
Technical info:
There is a crash somewhere in messenger's uxcore.dll, due to something to do with rpc, if you close a chat window while holding an ITextDocument pointer for the input field and then calling Release (i.e. Python deletes the object).

Comment 12 by mdcurran (in reply to comment 11) on 2013-06-09 23:40
Replying to Brendon22:

Did you ever find out why uxcore.dll was crashing this program?

No not yet. I shall post here if I ever work anything out.

In #1356 (comment) it is suggested that this is specific to WLM's text controls, not text controls in general.

Windows Live Messenger has been discontinued. Closing.