Open Bug 1208664 Opened 9 years ago Updated 2 years ago

Dump the final composited image and correlate it with paints

Categories

(Core :: Graphics: Layers, defect, P3)

defect

Tracking

()

Tracking Status
firefox44 --- affected

People

(Reporter: botond, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(1 file)

As a complement to the dumping of client-side layer textures in bug 1208661, it's nice to be able to dump the final composited images, and correlate them with the paints that are being composited.

We currently have code to dump the final composited image, but it suffers from two issues:

  (1) It's printed to the same file / stream as client-side textures.
      As the client-side textures and the composited image are
      dumped by different threads, there is a risk of the outputs
      being interleaved. Therefore, the composited images should be
      dumped to a different set of files.

  (2) Since client-side and compositor-side dumps go to different
      files, it would be nice to be able to correlate the two, so
      that you can tell which set of painted textures went into
      producing which composited image.

I have local patches that do this, but they're very hacky; among other things, they're specific to CompositorOGL, and specific to parent-process painting. I'm not sure how landable they are, but I'll post them anyways.
Depends on: 1206915
Bug 1208664 - Dump the final composited image and correlate it with paints. r=mattwoodrow
This is my very hacky and not-really-landable patch. I'll think about how to clean it up and make it landable.
Assignee: nobody → botond
Status: NEW → ASSIGNED
Whiteboard: [gfx-noted]
Jamie, a tip for unbitrotting this: the condition |gfxUtils::sDumpPainting| should now be |gfxEnv::DumpPaint()|, and the environment variable to turn it on would be MOZ_DUMP_PAINT.
(And sorry that I haven't landed this yet. The main reason is that the handling of the correlation with paint sequence numbers is very hacky, and I'd like to do it more nicely in the version I land.)

I haven't needed to use this in a while and probably not worth spending time unbitrotting it and cleaning it up until I do.

Assignee: botond → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: