# Problem testing/exporting in gitlab pipeline because of FMOD
**URL:** https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481
**Category:** Unity
**Created:** [November 27, 2020, 12:09am UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481 "2020-11-27T00:09:29Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@CrossingMoon](https://qa.fmod.com/u/CrossingMoon)
#### Post date: [November 27, 2020, 12:09am UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481/1 "2020-11-27T00:09:29Z")
Hello, our group has a unity project that locally (Windows Powershell) is able to be exported and tested without problem but when we try to do the same in our gitlab pipeline it fails.
This first stack frame is for the testing job:
Refreshing native plugins compatible for Editor in 24.56 ms, found 5 plugins.
Caught fatal signal - signo:11 code:1 errno:0 addr:0x48
Obtained 42 stack frames.
#0 0x007f24bdb28cf9 in FMOD\_Thread\_SetAttributes
#1 0x007f24bd7d960b in FMOD::getGlobals(FMOD::Global\*\*)
#2 0x007f24bd71e166 in \_init
#3 0x007f25d2c278f3 in \_dl\_rtld\_di\_serinfo
#4 0x007f25d2c2c3bf in \_dl\_find\_dso\_for\_object
#5 0x007f25c3b9e1ef in \_dl\_catch\_exception
#6 0x007f25d2c2b98a in \_dl\_find\_dso\_for\_object
#7 0x007f25c78c4f96 in (Unknown)
#8 0x007f25c3b9e1ef in \_dl\_catch\_exception
#9 0x007f25c3b9e27f in \_dl\_catch\_error
#10 0x007f25c78c5745 in dlerror
#11 0x007f25c78c5051 in dlopen
#12 0x00561fe8dfaaba in LoadPluginExecutable(char const\*, bool)
#13 0x00561fe8dfcaec in FindAndLoadUnityPlugin(char const\*, void\*\*)
#14 0x007f24c5a0b4c6 in mono\_lookup\_pinvoke\_call
#15 0x007f24c5a1e835 in mono\_marshal\_string\_to\_utf16
#16 0x007f24c58dfb24 in mono\_set\_break\_policy
#17 0x007f24c58c70d6 in \_init
#18 0x007f24c58c8b4e in \_init
#19 0x007f24c58cc846 in mono\_print\_method\_from\_ip
#20 0x007f24c5949ba2 in mono\_print\_thread\_dump\_from\_ctx
#21 0x007f24c5949ed1 in mono\_print\_thread\_dump\_from\_ctx
#22 0x0000004095e393 in (Unknown)
#23 0x0000004169dd54 in FMODUnity.EditorUtils:Update ()
#24 0x007f24c58cd8f9 in mono\_print\_method\_from\_ip
#25 0x007f24c5a3a0af in mono\_perfcounter\_foreach
#26 0x007f24c5a42139 in mono\_runtime\_run\_main
#27 0x007f24c5a04d6f in mono\_install\_unhandled\_exception\_hook
#28 0x00000041452b89 in (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
#29 0x0000004143fe08 in System.Reflection.MethodBase:Invoke (object,object[])
#30 0x007f24c58cd8f9 in mono\_print\_method\_from\_ip
#31 0x007f24c5a3a0af in mono\_perfcounter\_foreach
#32 0x007f24c5a3af5c in mono\_runtime\_invoke
#33 0x00561fe73bc1e3 in mono\_runtime\_invoke\_profiled(MonoMethod\*, ScriptingObjectPtr, void\*\*, MonoException\*\*, MonoClass\*)
#34 0x00561fe93f9152 in CallStaticMonoMethod(char const\*, char const\*, void\*\*, ScriptingExceptionPtr\*)
#35 0x00561fe93f8ed7 in CallStaticMonoMethod(char const\*, char const\*, void\*\*)
#36 0x00561fe6e1db12 in Application::TickTimer()
#37 0x00561fe7aa627b in MainMessageIteration(void\*)
#38 0x00561fe7aa613f in InitializeUnity(void\*)
#39 0x00561fe7aa5261 in main
#40 0x007f25c3a58bf7 in \_\_libc\_start\_main
#41 0x00561fe618d06f in \_start
Aborted (core dumped)
This is for the export job:
`Obtained 4 stack frames.` `#0 0x0055f859e86a85 in AudioManager::systemCallback(FMOD_SYSTEM*, FMOD_SYSTEM_CALLBACKTYPE, void*, void*)` `#1 0x0055f85dc193b4 in FMOD::Thread::callback(void*)` `#2 0x007f37f58fb609 in start_thread` `#3 0x007f37f5822293 in clone` `Aborted (core dumped)`
Anyone with a similar problem and a possible solution?
Unity: 2019.3.6f1
Thank you in advance.
Eduardo
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [December 4, 2020, 4:29am UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481/2 "2020-12-04T04:29:29Z")
What version of FMOD are you using?
Are you able to share your entire output log at all?
---
### Author:  [@CrossingMoon](https://qa.fmod.com/u/CrossingMoon)
#### Post date: [December 4, 2020, 10:55am UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481/3 "2020-12-04T10:55:04Z")
Hello 2.01.00 version and this is the log[log.txt](https://qa.fmod.com/uploads/short-url/uErFDLj6w68qDaNPMVw5BGiAQz1.txt) (927.1 KB)
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [December 10, 2020, 1:09am UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481/4 "2020-12-10T01:09:13Z")
It looks like it is having trouble finding the fmod libs.
```auto
Reloading assemblies after forced synchronous recompile.
Begin MonoManager ReloadAssembly
Fallback handler could not load library /opt/unity/Editor/Data/Mono/lib/libfmodstudioL
Fallback handler could not load library /opt/unity/Editor/Data/Mono/lib/libfmodstudioL.so
Fallback handler could not load library /opt/unity/Editor/Data/Mono/lib/fmodstudioL
Fallback handler could not load library /opt/unity/Editor/Data/Mono/lib/libfmodstudioL
Fallback handler could not load library /opt/unity/Editor/Data/Mono/lib/libfmodstudioL.so
Fallback handler could not load library /opt/unity/Editor/Data/Mono/lib/libfmodstudioL
```
---
### Author:  [@megaleon](https://qa.fmod.com/u/megaleon)
#### Post date: [August 3, 2023, 4:49pm UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481/5 "2023-08-03T16:49:10Z")
> [@cameron-fmod](#):
>
> `Fallback handler could not load library`
Is there a solution regarding this, I’m having exactly this problem at the moment.
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [August 21, 2023, 1:25am UTC](https://qa.fmod.com/t/problem-testing-exporting-in-gitlab-pipeline-because-of-fmod/16481/6 "2023-08-21T01:25:24Z")
It looks like this issue has been resolved in another thread:
> [@Docker Windows “DllNotFoundException: fmodstudioL”](https://qa.fmod.com/t/docker-windows-dllnotfoundexception-fmodstudiol/20491/14):
>
> Nah, we don’t like that conclusion. We believe we’ve got fixes for both the issues you ran into and we’re working to get them into a future release. Thanks for your sleuthing and detailed repro info. Cheers