Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fontawesome-webfont.ttf file gets locked by system process on Windows 2016 #1

Closed
andreas-cloudnine opened this issue Apr 6, 2017 · 3 comments
Assignees
Labels

Comments

@andreas-cloudnine
Copy link

Hi,

We are using Epi.FontThumbnail on a EPiServer site (version 10.4.2) and sometimes when we build via TeamCity to a Windows 2016 server we get an error saying the font file fontawesome-webfont.ttf is locked by the SYSTEM process. We then have to do an iisreset and delete the font to get it to build again. This only happens rarely (three times so far in about a months time).

I have found the following Stack Overflow thread, but it does not give a solution to the issue:

http://stackoverflow.com/questions/27677285/font-file-is-being-held-by-system-process

Is it possible to embed the font file in the assembly or similar to avoid this issue?

@degborta
Copy link
Collaborator

degborta commented Apr 7, 2017

Thanks for the input, I will have a look at it!

@degborta degborta self-assigned this Apr 7, 2017
@degborta degborta added the bug label Apr 7, 2017
@degborta
Copy link
Collaborator

@andreas-cloudnine Sorry for the delay :( I have done some changes to fix the issue you were having. The font is now an embedded resource and I have also done some changes to how the images are loaded (also to prevent locking of the generated images).

New version is uploaded to Episerver nuget feed and waiting for approval.

Get back to me with feedback if it solves the problems you were having.

Thanks!

@andreas-cloudnine
Copy link
Author

It seems to work fine. We haven't had any issues since updating the NuGet package. I'll do a pull request if there are any other issues in the future instead of just suggesting a fix.

Thanks for the effort!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants