"Crash" while entering search argument

Page 1 of 1 (4 items)
This post has 3 Replies | 1 Follower

Posts 24401
Forum MVP
MJ. Smith | Forum Activity | Posted: Sat, May 14 2016 3:13 PM

One of the common "crashes" I was simply entering the next letter. 7167.Verbum Log Files.zip

Application: Verbum.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in async work
Stack:
   at System.Environment.FailFast(System.String, System.Exception)
   at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object)
   at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Faulting application name: Verbum.exe, version: 6.12.0.16, time stamp: 0x5730d9f9
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007ffc421084ed
Faulting process id: 0x28d4
Faulting application start time: 0x01d1ae18883ad0e6
Faulting application path: C:\Users\mjesp_000\AppData\Local\Verbum\System\Verbum.exe
Faulting module path: unknown
Report Id: 08ec19d6-c641-442b-89ed-cce0ac87309a
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: LogosCEF.exe, version: 1.2.1.7, time stamp: 0x55f72ea9
Faulting module name: libcef.dll, version: 3.2454.1317.0, time stamp: 0x55de8d5f
Exception code: 0xc0000005
Fault offset: 0x0000000000684972
Faulting process id: 0x1a04
Faulting application start time: 0x01d1ae190c9d4505
Faulting application path: C:\Users\mjesp_000\AppData\Local\Verbum\System\LogosCEF.exe
Faulting module path: C:\Users\mjesp_000\AppData\Local\Verbum\System\libcef.dll
Report Id: ba5be16f-9cfd-4bb2-8598-88ef88031ed2
Faulting package full name:
Faulting package-relative application ID:

Orthodox Bishop Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."

Posts 9944
George Somsel | Forum Activity | Replied: Sat, May 14 2016 3:19 PM

MJ. Smith:
One of the common "crashes" I was simply entering the next letter.

Is the crash possibly due to the fact that your library ("liberry" for those in Rio Linda)?

george
gfsomsel

יְמֵי־שְׁנוֹתֵינוּ בָהֶם שִׁבְעִים שָׁנָה וְאִם בִּגְבוּרֹת שְׁמוֹנִים שָׁנָה וְרָהְבָּם עָמָל וָאָוֶן

Posts 7440
LogosEmployee

Same crash as https://community.logos.com/forums/t/126054.aspx

It will be fixed in the next beta.

Posts 1753
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Tue, May 31 2016 3:27 PM

This crash is now fixed in 6.12.

Page 1 of 1 (4 items) | RSS