Don't call SessionAccessibility.NativeProvider.setAttached until native handle is set
Categories
(GeckoView :: General, defect)
Tracking
(firefox137 wontfix, firefox138 wontfix, firefox139 fixed)
People
(Reporter: m_kato, Assigned: m_kato)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
This issue is a possible crash case.
Actually SessionAccessibility.NativeProvider.setAttached is called in C++ constructor of SessionAccessibility. But native handle is set after calling the constructor. So when NativeProvider.setAttached is called, C++ side might not set native handle yet.
So we should not call setAttached in the constructor.
| Assignee | ||
Comment 1•8 months ago
|
||
This issue is a possible crash case.
Actually SessionAccessibility.NativeProvider.setAttached is called in
C++ constructor of SessionAccessibility. But native handle is set
after calling the constructor. So when NativeProvider.setAttached is
called, C++ side might not set native handle yet.
So we should not call setAttached in the constructor.
Comment 3•7 months ago
|
||
| bugherder | ||
Updated•7 months ago
|
Comment 4•7 months ago
|
||
The patch landed in nightly and beta is affected.
:m_kato, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox138towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•7 months ago
|
| Assignee | ||
Comment 5•7 months ago
|
||
bp-ab7644f8-2186-40e5-b8f5-e63780250428 is exactly this situation
Description
•