[Ultimate PDF] Failed to launch Chromium! [0819/001522.180:FATAL:feature_list.cc(282)] Check failed:
Forge component by Leonardo Fernandes
Application Type
Traditional Web

Hi we are encountering this error and we can't figure out what causes this error. Can you help us on how to resolved this issue. This error appears after we upgrade our platform version 

OS platform version: 11.12.0

Error Message:
Failed to launch Chromium! [0819/001522.180:FATAL:feature_list.cc(282)] Check failed: !g_initialized_from_accessor.
Backtrace:
ovly_debug_event [0x00007FFA03551252+16183762]
ovly_debug_event [0x00007FFA03550832+16181170]
ovly_debug_event [0x00007FFA03563383+16257795]
ovly_debug_event [0x00007FFA03553386+16192262]
ovly_debug_event [0x00007FFA030A4B2E+11283118]
ovly_debug_event [0x00007FFA034CDB58+15645400]
ovly_debug_event [0x00007FFA034CDACD+15645261]
ovly_debug_event [0x00007FFA034F8F28+15822504]
ovly_debug_event [0x00007FFA034CD35E+15643358]
ovly_debug_event [0x00007FFA034F83E3+15819619]
ovly_debug_event [0x00007FFA034F82BB+15819323]
ovly_debug_event [0x00007FFA034F80F2+15818866]
ChromeMain [0x00007FFA025E11B6+286]
Ordinal0 [0x00007FF60244275F+10079]
Ordinal0 [0x00007FF60244182D+6189]
GetHandleVerifier [0x00007FF60254B7C2+697538]
BaseThreadInitThunk [0x00007FFA378D84D4+20]
RtlUserThreadStart [0x00007FFA3A381781+33]

We are using the old version of the UltimatePDF

Hi @froilan ,

It should not happen but do check for any thing missing to pass for component and try to debug  

Also , in my customer's environment, after updating Forge, I got the following error in PDF and PNG output.

After investigating, it seems that the cause is that the Chromium revision being downloaded is old.

I used Server Action "UseBrowser"(Module:UltimatePDF) and specified the revision number as the latest version of chromium, and the download was completed.

Is it possible to make this PDF output without explicitly specifying the revision?


-OutSystems Platform Version 11.11.3 / On-Premise

- Windows Server 2016 / Ver1607

- OLD Ultimate PDF 3.0.4

- Current Ultimate PDF 4.0.1


Revision of Chromium

 Revision downloaded by default: 848005

 Explicitly specified revision: 917269
    --- Referenced : chromium website


Error Trace

[0901/181809.905:ERROR:os_crypt_win.cc(70)] Failed to encrypt: The system cannot find the file specified. (0x2)
[0901/181809.905:FATAL:headless_browser_main_parts.cc(103)] Check failed: OSCrypt::Init(local_state_.get()). 
Backtrace:
	IsSandboxedProcess [0x00007FFDFF441842+705042]
	IsSandboxedProcess [0x00007FFDFF3C39A2+189298]
	IsSandboxedProcess [0x00007FFDFF3D2AF8+251080]
	IsSandboxedProcess [0x00007FFDFF3D39E0+254896]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x00007FFE00C12123+12980755]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x00007FFE00C11E8D+12980093]
	ovly_debug_event [0x00007FFDFDA05929+16331561]
	ovly_debug_event [0x00007FFDFDDC5B17+20264215]
	ovly_debug_event [0x00007FFDFDA04675+16326773]
	ovly_debug_event [0x00007FFDFDA073BE+16338366]
	IsSandboxedProcess [0x00007FFDFFEB7DB7+11675527]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF35A837+8179991]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF35B5AD+8183437]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF35B20C+8182508]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF35A1BD+8178333]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF35A53A+8179226]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF394D1A+8418810]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF394BDC+8418492]
	CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFF3949E7+8417991]
	ChromeMain [0x00007FFDFCA71238+408]
	Ordinal0 [0x00007FF7AA8826B8+9912]
	Ordinal0 [0x00007FF7AA881A41+6721]
	GetHandleVerifier [0x00007FF7AA9CAF42+904642]
	BaseThreadInitThunk [0x00007FFE4F4884D4+20]
	RtlUserThreadStart [0x00007FFE4F5C1781+33]
mvp_badge
MVP

Hi. Both of these errors should be fixed by the version 4.0.2.

You can also change the default revision in this site property:


Thank you for your prompt reply and correction.

I immediately tried it in my environment, but I got the same error.

However, when I specified the revision in the site properties, the download succeeded! I'd like to deal with it here for now.

By the way, does it work in other environments without specifying the revision?

Also, I would appreciate it if you could tell me what the logic is for determining the revisions that Forge gets.


Looks like we need to upgrade the version of the UltimatePDF that we are using. We are using the old version and the data type of the site property differs from the solution you suggests. Thanks

mvp_badge
MVP

Please try again with the default site property and let me know the results. With this new release, that error should mark the release as faulty, and on the next try it should delete it and download it again.

Yes, it works in other environments without requiring change in the site property. Including my personal environment: https://leonardofernandes.outsystemscloud.com/UltimatePDF_Demo/


The default revision is chosen by the Puppeteer version being used. It is built to download a specific Chromium version, which it was tested against.

mvp_badge
MVP


In this case you can simply set it to the revision number that you want.

Hi Leonardo, If i may ask, where can I find the Chromium and its version? 

mvp_badge
MVP

You can download the latest revision in the link below. You can also find a link to commondatastorage.googleapis.com to browse the history of Chromium revisions.

https://www.chromium.org/getting-involved/download-chromium


Note that there's no guarantee on the quality of each revision. All revisions are nightly builds, and can be unstable.

The revision that Ultimate PDF uses by default is considered stable, since it has been tested with.

> Please try again with the default site property and let me know the results.

An error will occur if the default site property values are used. Here is the Stack Trace.


Stack

Failed to launch browser! [0906/183317.398:ERROR:os_crypt_win.cc(70)] Failed to encrypt: The system cannot find the file specified. (0x2)

[0906/183317.398:FATAL:headless_browser_main_parts.cc(103)] Check failed: OSCrypt::Init(local_state_.get()).

Backtrace:

IsSandboxedProcess [0x00007FFDFFF41842+705042]

IsSandboxedProcess [0x00007FFDFFEC39A2+189298]

IsSandboxedProcess [0x00007FFDFFED2AF8+251080]

IsSandboxedProcess [0x00007FFDFFED39E0+254896]

RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x00007FFE01712123+12980755]

RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x00007FFE01711E8D+12980093]

ovly_debug_event [0x00007FFDFE505929+16331561]

ovly_debug_event [0x00007FFDFE8C5B17+20264215]

ovly_debug_event [0x00007FFDFE504675+16326773]

ovly_debug_event [0x00007FFDFE5073BE+16338366]

IsSandboxedProcess [0x00007FFE009B7DB7+11675527]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE5A837+8179991]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE5B5AD+8183437]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE5B20C+8182508]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE5A1BD+8178333]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE5A53A+8179226]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE94D1A+8418810]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE94BDC+8418492]

CrashForExceptionInNonABICompliantCodeRange [0x00007FFDFFE949E7+8417991]

ChromeMain [0x00007FFDFD571238+408]

Ordinal0 [0x00007FF619C026B8+9912]

Ordinal0 [0x00007FF619C01A41+6721]

GetHandleVerifier [0x00007FF619D4AF42+904642]

BaseThreadInitThunk [0x00007FFE4F4884D4+20]

RtlUserThreadStart [0x00007FFE4F5C1781+33]


[0906/183317.538:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL isswiftshader


   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at PuppeteerSharp.States.ChromiumStartingState.<StartCoreAsync>d__6.MoveNext() in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\States\ChromiumStartingState.cs:line 83

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at PuppeteerSharp.States.ChromiumStartingState.<StartCoreAsync>d__6.MoveNext() in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\States\ChromiumStartingState.cs:line 89

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at PuppeteerSharp.Launcher.<LaunchAsync>d__8.MoveNext() in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Launcher.cs:line 63

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at PuppeteerSharp.Launcher.<LaunchAsync>d__8.MoveNext() in C:\projects\puppeteer-sharp\lib\PuppeteerSharp\Launcher.cs:line 86

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at OutSystems.NssUltimatePDF_Service.BrowserExecution.BrowserInstancePool.<NewBrowserContext>d__9.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at OutSystems.NssUltimatePDF_Service.BrowserExecution.BrowserInstancePool.<NewPageOnNewBrowserContext>d__10.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at OutSystems.NssUltimatePDF_Service.BrowserExecution.BrowserExecutionContext.<PrintPDF>d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at OutSystems.NssUltimatePDF_Service.Utils.AsyncUtils.StartAndWait[T](Func`1 async)

   at OutSystems.NssUltimatePDF_Service.CssUltimatePDF_Service.MssPrintPDF(String ssURL, RLCookieRecordList ssCookies, String ssBrowserRevision, RCViewportRecord ssViewport, RCPaperRecord ssPaper, String ssTemporaryFolder, Byte[]& ssPDF)


   at ssUltimatePDF_Service.RssExtensionUltimatePDF_Service.MssPrintPDFExt(HeContext heContext, String inParamURL, RecordList inParamCookies, String inParamBrowserRevision, IRecord inParamViewport, IRecord inParamPaper, String inParamTemporaryFolder, Byte[]& outParamPDF)

mvp_badge
MVP

Regarding the issue "Failed to encrypt: The system cannot find the file specified", this is indeed fixed by a newer Chromium version. The default release being used by Ultimate PDF is 884014. So you can update the site property DefaultBrowserRevision to a more recent release (e.g. set it to chrome@890410 according to one of the stackoverflow links below).

However, the demo module has a bug which in practice ignores the value of the site property. The bug is caused by using the UseBrowser action. If you delete that action from the demo module, it should start using the site property. This will be fixed in the next release. Just delete the following node in the demo module:


I cannot test this workaround, because the issue is not reproduced in my environment. But I would appreciate if anyone can confirm that it indeed fixes the issue, so I can change the default revision in the next version.


More information on the cause of the issue:

https://github.com/hardkoded/puppeteer-sharp/issues/1684

https://stackoverflow.com/questions/66921026/puppeteer-sharp-failed-to-launch-base

https://github.com/microsoft/playwright/issues/5197

Hi Leonardo,

The action UseBrowser in our use case is not used to generate the PDF, so i think the reason is not there.

mvp_badge
MVP

Please use the latest release, 4.0.4, which has updated to a more recent Chromium revision.

The version you have installed was downloading revision 848005 (as Reishi pointed out) and not the 884014 (as I incorrectly stated). The issue was fixed on the revision 849347, so the default revision was indeed faulty. Just updating the PuppeteerSharp library to the latest version was enough to use a newer revision, which includes the fix already.

Thanks for the quick fix and release!

I have updated the Forge component in my environment and have confirmed that the PDF output is successful.


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.