| Summary: | Mini browser immediately hit an assertion in debug build | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> | ||||
| Component: | WebKit Misc. | Assignee: | Ryosuke Niwa <rniwa> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | cdumez, eric.carlson, ews-watchlist, glenn, jer.noble, philipj, sergio, simon.fraser, webkit-bug-importer, youennf | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=209422 | ||||||
| Attachments: |
|
||||||
|
Description
Ryosuke Niwa
2020-03-25 18:51:42 PDT
Created attachment 394566 [details]
Fixes the bug
Comment on attachment 394566 [details]
Fixes the bug
Should you have used ObjecdtIdentifer instead of 0 or 1?
(In reply to Simon Fraser (smfr) from comment #2) > Comment on attachment 394566 [details] > Fixes the bug > > Should you have used ObjecdtIdentifer instead of 0 or 1? I don't think so. There is no object to identify. This is really a singleton. It's actually wrong that we're using message receiver map for this. We should just hard-code it in WebProcess's message dispatcher instead. But for now, this will fix the assertion failure that happens at launch. Committed r259028: <https://trac.webkit.org/changeset/259028> |