Crash when accessing ScriptMessage.frame if the corresponding frame has been destroyed
Bug #1442969 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Fix Released
|
High
|
Chris Coulson | ||
Bug Description
Accessing ScriptMessage.frame after the frame has been destroyed causes a null pointer deref
Related branches
| Changed in oxide: | |
| milestone: | none → branch-1.7 |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
| importance: | Undecided → High |
| status: | New → Fix Released |
To post a comment you must log in.
