Generated PDF file lock not released before callback fired

[santiagoIT]

Hi there,

This is a problem I have run into using CEFSharp, which is really just a simple .NET wrapper around CEF.

The problem is that if you try to access the generated PDF file directly after the callback function has been fired an IO exception is raised indicating that the file is still in use. When CEF fires the CefPdfPrintCallback::OnPdfPrintFinished callback the file lock on the generated PDF file has not yet been released.
If you however wait for a few ms before attempting to access the generated PDF file, it then works -> NO IO.Exception.

Windows 10 x64, CefSharp v51.0.0.
Problem could be reproduced with both the regular and offscreen browsers.

Is this expected behaviour/as designed?

To me it seems like a bug, it would be better if the file lock is released before the callback is executed.

Here is the link to the issue I filed for the CefSharp project with some more information.

https://github.com/cefsharp/CefSharp/issues/1807#issuecomment-249059697

Thank you!

[magreenblatt]

What CEF version? Is it only a problem when you try to delete or move the file, or also to read the file?

[sigh71]

I am experiencing this problem now with CEF 59 used with CEFGlue.
I am only attempting to read the file.

Code: Select all

using (var fileStream = new FileStream(path, FileMode.Open, FileAccess.Read))

It is especially repeatable if you create 2 pdfs from two different browsers in quick succession, the first will not be locked, but the second will be locked in the callback.