Bug 1677194 Comment 10 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Oh, I see. Let me try again.
Revision 1 by
on 
Oh, I see. Let me try again.

Well, though, it looks to me that the incorrect access reported by ASAN already occurs by that time, so 
I am not sure what we should do about it.

The symptom noticed here has already been caused by some free/poison action without invalidating a pointer value in a a variable (or two?)
Revision 2 by
on 
Oh, I see. Let me try again.

Well, though, it looks to me that the incorrect access reported by ASAN already occurs by that time, so 
I am not sure what we should do about it.
Aha, now I see it. The problem could also happen at the reference of mUpdateBatchNest. That can be solved by the check.

(If not, the symptom noticed here may have already been caused by some free/poison action without invalidating a pointer value in a a variable (or two?)

Back to Bug 1677194 Comment 10