The presence of an external_id and non-zero compositor_ref will at least tell us that it should be able to be mapped in by the compositor process. To explain a bit more what I'm looking for: This indicates a defect in one or more memory reporters. │ │ │ │ │ └────258,128 B (00.07%) ── sourceĪlso, the GPU process section of about:memory warns: WARNING: the following values are negative or unreasonably large.
The web console warns: Cannot access blob URL “blob:” from a different agent cluster.Ĭannot access blob URL “blob:” from a different agent cluster. The inspector shows the blank image element is: Potentially you could use the dev tools to find the uri of the image in question and then use a verbose memory report to find that uri, it would have information about what imagelib thinks is the status of the image.
(In reply to Timothy Nikkel (:tnikkel) from comment #1)
0 kommentar(er)
