OOPS rendering blueprint dependency graph. Subprocess couldn't allocate memory

[Diogo Matsubara]

As seen in OOPS-818C616, the code that generates the dependency graph starts a subprocess to get the job done. This subprocess crashed with an OSError: [Errno 12] Cannot allocate memory causing the page to render an OOPS

[Curtis Hovey (sinzui)]

I have a branch that fixes this issue by directly recording the errors when an exception is raised by the renderGraphvizGraph() method. The spec index page will continue to display, though without the image map and possibly the dependency graph image too.

Diogo suggested that we load an alternate image when the image fails to load. I like
the idea. In the cases we are seeing now, the error is occurring in the system, not the application. The error probably will not happen happen when the page is reloaded.

Attached is a screen cap of the forced error condition happening both for the image map
and later when the image is loaded. I would like these message review before I submit the code for review.

[Curtis Hovey (sinzui)]

I have a branch that fixes the issue.

[Curtis Hovey (sinzui)]

Fixed in RF 6014.

[Curtis Hovey (sinzui)]

Fixed released in version 1.2.4.