Welcome Guest Search | Active Topics | Sign In | Register

Child process failure - and causes subsequent failures Options
Phil
Posted: Tuesday, March 22, 2022 6:27:10 AM
Rank: Advanced Member
Groups: Member

Joined: 11/8/2017
Posts: 66
Hello, we are running EO-PDF (latest - v22.0.40) from a .NET-Core 3.1 web application. We are deploying to App-Services. When we request a report, initially the requests are OK, however eventually we seem to get a "Child process exited unexpectedly" as follows:-

Child process exited unexpectedly.
at System.Environment.get_StackTrace()
at EO.Base.BaseException..ctor(String lsy, Exception lsz)
at EO.Internal.qsep.ywtv..ctor(ywtu noc, String nod)
at EO.Internal.qsep.ywtv..ctor(ywtu noe)
at EO.Internal.qsep.chnc(qsam nnn)
at EO.Internal.qsep.chmn(Boolean& nmk, qses[] nml, String nmm, String nmn)
at EO.Internal.qsep.isvh(qses[] nmh, String nmi, String nmj)
at EO.Internal.qseq.isvh(String nro, String nrp)
at EO.Internal.yrnl.pdbv()
at EO.Internal.yrnl.uqbu.ybkh()
at EO.Internal.qsac.ekjd(Action lum)
at EO.Internal.yrnl.ytmc(WindowsIdentity fs)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.WebEngine.Engine.Start()
at EO.Internal.wsus.wvrr()
at EO.Internal.wsut.wvrr(wsus& bra)
at EO.Internal.wsuu.wvrr(yrng bre, wsus& brf)
at EO.Internal.wsux.npeq()
at EO.Internal.wsux..ctor(yrng brj, HtmlToPdfOptions brk)
at EO.Pdf.HtmlToPdfSession.xdlp(HtmlToPdfOptions ys)
at EO.Pdf.HtmlToPdfSession..ctor(HtmlToPdfOptions yp, HtmlToPdfSession yq, ResourceHandler yr)
at EO.Pdf.HtmlToPdfSession.Create(HtmlToPdfOptions options, ResourceHandler resourceHandler)
at EO.Pdf.HtmlToPdf.xphi.yjfm()
at EO.Internal.wsuu.jnds[a](qrzb`1 bri)
at EO.Pdf.HtmlToPdf.ConvertHtml(String html, PdfDocument doc, HtmlToPdfOptions options)
at EO.Pdf.HtmlToPdf.ConvertHtml(String html, Stream stream, HtmlToPdfOptions options)
at EO.Pdf.HtmlToPdf.ConvertHtml(String html, Stream stream)
at MI.ParentReporting.Web.PdfGenerate.NetCore.Controllers.PdfGenerateController.GeneratedPdf(UploadData uploadData, Int32& pageCount, HtmlToPdfResult& coversheetHtmlToPdfResult, Byte[]& coversheetPdf, Boolean generateFromCoversheetHtml) in e:\DevOpsBuilds\7\s\MI.ParentReporting.Web.PdfGenerate.NetCore\Controllers\PdfGenerateController.cs:line 649
at MI.ParentReporting.Web.PdfGenerate.NetCore.Controllers.PdfGenerateController.Post(UploadData uploadData) in e:\DevOpsBuilds\7\s\MI.ParentReporting.Web.PdfGenerate.NetCore\Controllers\PdfGenerateController.cs:line 104
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at MI.ParentReporting.Web.PdfGenerate.NetCore.Controllers.PdfGenerateController.Post(UploadData uploadData)
at lambda_method(Closure , Object , Object[] )
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Logged|12_1(ControllerActionInvoker invoker)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Logged|12_1(ControllerActionInvoker invoker)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
at Microsoft.AspNetCore.Mvc.Routing.ActionEndpointFactory.<>c__DisplayClass7_0.<CreateRequestDelegate>b__0(HttpContext context)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.Invoke(HttpContext context)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContext.HandleRequest()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContext.HandleRequest()
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContext.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

After the above occurs, subsequent requests often fail

I have created an Azure memory dump and sent it to your private email address

Can you help ?
eo_support
Posted: Thursday, March 24, 2022 8:00:43 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

We recently fixed a handle/memory leak in our HTML to PDF converter that might be the root cause of this problem. We will have a new build either this week or early next week with this issue fixed. So you can try the new build and see if that resolves the issue for you.

If the problem continues with the new build, please try to capture debug log when the failure occurs and send the log to us. You would capture it like this:

Code: C#
try
{
   HtmlToPdf.ConvertHtml(...);
}
catch
{
    string log = EO.Base.Runtime.GetLogs();
   //send the log to us
}


Once we have that log we will see what we can find.

Thanks!
Phil
Posted: Friday, March 25, 2022 6:04:15 AM
Rank: Advanced Member
Groups: Member

Joined: 11/8/2017
Posts: 66
Hello, thanks for the reply - we currently have the latest version available (v22.0.40) installed - this is the version we have the posted issue against

I have added the (try/catch) code you have suggested in your reply and will send you logs when we next get the failure

Kind regards
Phil
eo_support
Posted: Friday, March 25, 2022 8:13:11 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

Build 22.0.40 is the one that has the leak issue and we will have a new build today (build 22.0.68) with the fix. So please try that build first once it's out.

Thanks!
Phil
Posted: Tuesday, April 5, 2022 10:05:17 PM
Rank: Advanced Member
Groups: Member

Joined: 11/8/2017
Posts: 66
fyi, we have upgraded to 22.0.68 and done some testing - the issue looks to have been resolved

Many thanks for the turn-around

Kind regards
Phil
eo_support
Posted: Wednesday, April 6, 2022 9:58:48 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Great. Glad to hear that it works for you! Please feel free to let us know if there is anything else.


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.