RE: Null Reference Exception after Forms.TabPageCollection.Remove(
- From: v-lliu@xxxxxxxxxxxxxxxxxxxx (Linda Liu [MSFT])
- Date: Wed, 21 Mar 2007 10:38:25 GMT
Hi Dave,
Thank you for your prompt response.
Sorry that I didn't clarify in my previous reply.
The KB 893005 was addressing a case whose scenario was different from
yours, but with similar symptoms(the call stack of this case when the
exception occurs is the same as your program's).
In that case, an object which is subclassed by the ToolTip can throw an
exception if an error occurs while unsubclassing the control. The Framework
wouldn't detect this situation correctly and could free the subclass
procedure's memory while it was still set to be the control's window
procedure.
In addition, there're several cases recorded in our inner data base, whose
scenarios are different, but with the similar symptoms as your program.
They were all solved by the hotfix 893005.
Please give hotfix 893005 a try and let me know if it works.
Sincerely,
Linda Liu
Microsoft Online Community Support
.
- References:
- Null Reference Exception after Forms.TabPageCollection.Remove() ca
- From: Dave Leach
- RE: Null Reference Exception after Forms.TabPageCollection.Remove() ca
- From: Linda Liu [MSFT]
- RE: Null Reference Exception after Forms.TabPageCollection.Remove(
- From: Dave Leach
- RE: Null Reference Exception after Forms.TabPageCollection.Remove(
- From: Linda Liu [MSFT]
- Null Reference Exception after Forms.TabPageCollection.Remove() ca
- Prev by Date: Binding semantics when the model is changed
- Next by Date: Re: Binding semantics when the model is changed
- Previous by thread: RE: Null Reference Exception after Forms.TabPageCollection.Remove(
- Next by thread: Re: Null Reference Exception after Forms.TabPageCollection.Remove() ca
- Index(es):
Relevant Pages
|