We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description There is a null pointer access issue in b861ff2, which ends up crashing application immediately after you start composing text.
Steps to reproduce Steps to reproduce the behavior:
notepad.exe
Expected behavior No application crash.
Actual behavior It's crashing here.
mozc/src/win32/tip/tip_edit_session_impl.cc
Lines 455 to 456 in b861ff2
When TipCompositionUtil::GetComposition(context, write_cookie) returns nullptr, subsequent .As(&composition) ends up crashing.
TipCompositionUtil::GetComposition(context, write_cookie)
nullptr
.As(&composition)
Version or commit-id b861ff2
Environment
Additional Information The fix is on the way. We just need to check the return value, as it used to be. b861ff2#diff-1a5aa2b35b0e0b109860116f0280b9e3b641f0225f8304c7a3fd70e48a9382c9L454-R456
The text was updated successfully, but these errors were encountered:
497a6ae
No branches or pull requests
Description
There is a null pointer access issue in b861ff2, which ends up crashing application immediately after you start composing text.
Steps to reproduce
Steps to reproduce the behavior:
notepad.exe
Expected behavior
No application crash.
Actual behavior
It's crashing here.
mozc/src/win32/tip/tip_edit_session_impl.cc
Lines 455 to 456 in b861ff2
When
TipCompositionUtil::GetComposition(context, write_cookie)
returnsnullptr
, subsequent.As(&composition)
ends up crashing.Version or commit-id
b861ff2
Environment
Additional Information
The fix is on the way. We just need to check the return value, as it used to be.
b861ff2#diff-1a5aa2b35b0e0b109860116f0280b9e3b641f0225f8304c7a3fd70e48a9382c9L454-R456
The text was updated successfully, but these errors were encountered: