Cr_z_adler32_combine: An unhandled exception was encountered during a user callback

[ashemedai]

Using a supported version?

• I have searched searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Signal Desktop starts and real soon after crashes with this unhandled exception.

Steps to reproduce

1. Start Signal Desktop on Windows 10
2. Within a minute of starting it and seeing the GUI, WinDbg gets launched with this exception

Expected result

Signal Desktop just running.

Actual result

WinDbg !analyze -v gives this:

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff74d18311b (Signal!Cr_z_adler32_combine+0x000000000028f80b)
   ExceptionCode: c000041d
  ExceptionFlags: 00000001
NumberParameters: 0

FAULTING_THREAD:  00003620

PROCESS_NAME:  Signal.exe

ERROR_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.

EXCEPTION_CODE_STR:  c000041d

STACK_TEXT:  
00000071`b85f9cc0 00007ff7`4d184f52     : 00000000`00000000 00007ff7`50cf9170 00000071`b85f8808 00000071`b85f8830 : Signal!Cr_z_adler32_combine+0x28f80b
00000071`b85f9cf0 00007ff7`4a339cd9     : 00000000`00000000 00000000`00000741 00004f40`042d4300 00004f40`0025c018 : Signal!Cr_z_adler32_combine+0x291642
00000071`b85f9f50 00007ff7`4a2f86d1     : 04000238`00182188 00004a3f`780d0347 aaaaaaaa`aaaaaaaa aaaaaaaa`aaaaaaaa : Signal!v8::internal::ThreadIsolation::StartOfJitAllocationAt+0xff49
00000071`b85fa130 00007ff7`48b8be63     : 00000000`001283c5 00004f40`0025c040 00007ff7`4f4679d0 00004f40`00154000 : Signal!v8::Function::Call+0x1e1
00000071`b85fa220 00007ff7`48b8c3eb     : 00004f40`0025c018 00007ff7`4a2f7420 aaaaaaaa`00000000 00007ff7`4a415dd8 : Signal!node::CallbackScope::CallbackScope+0x6f3
00000071`b85fa380 00007ff7`48b8c262     : 00004f40`00128000 00000071`b85fa540 00000071`b85fa5d0 00000000`00000001 : Signal!node::MakeCallback+0x15b
00000071`b85fa440 00007ff7`48b8c089     : 00000071`b85fa5e8 00004f40`00195800 00004f40`04268fc0 00007ff7`48b8b757 : Signal!node::MakeCallback+0x1a2
00000071`b85fa4f0 00007ff7`46e16aca     : 00000071`b85fa720 00007ff7`4a2f4dfe 00004f40`0025c028 00007ff7`4a2f51eb : Signal!node::MakeCallback+0x89
00000071`b85fa590 00007ff7`46c6f9dd     : 00000000`00000080 00000071`b85fa6b8 00000000`00000000 00007ff7`46e16185 : Signal!std::__Cr::vector<v8::CpuProfileDeoptFrame,std::__Cr::allocator<v8::CpuProfileDeoptFrame> >::vector<v8::CpuProfileDeoptFrame,std::__Cr::allocator<v8::CpuProfileDeoptFrame> >+0x3e43a
00000071`b85fa670 00007ff7`46d05b31     : 00004f40`04357f00 00000071`b85fa801 00004f40`04057c40 00004f40`0414ade0 : Signal!node::loader::ModuleWrap::IsNotIndicativeOfMemoryLeakAtExit+0xd7ad
00000071`b85fa6f0 00007ff7`46d0a693     : 00000000`00000000 00000000`00000000 aaaaaaaa`aaaa0000 00000000`00000000 : Signal!uv_fs_get_statbuf+0x44f41
00000071`b85fa790 00007ff7`48075d49     : 00000000`00000000 00000000`00000000 aaaaaaaa`aaaa0000 00004f40`0414ade0 : Signal!uv_fs_get_statbuf+0x49aa3
00000071`b85fa7d0 00007ff7`4808445f     : 00000000`00000000 00004f40`003ace80 aaaaaaaa`aaaaaaaa 00007ff7`47fc6a94 : Signal!uv_timer_set_repeat+0x4cb039
00000071`b85fa900 00007ff7`4c75cd66     : 00004f40`04429f40 00000071`b85faa07 00007ff7`4c7ffe20 00004a3f`780d0ba7 : Signal!uv_timer_set_repeat+0x4d974f
00000071`b85faa00 00007ff7`4c767dfa     : 00004f40`0440c120 00007ff7`4886a722 00000000`00000000 00000000`00000000 : Signal!v8::internal::compiler::CompilationDependencies::PrepareInstallPredictable+0x785f86
00000071`b85faa30 00007ff7`4915f930     : 00000071`b85fabb8 00007ff7`4af8c147 00000000`000000d1 00000000`00000000 : Signal!v8::internal::compiler::CompilationDependencies::PrepareInstallPredictable+0x79101a
00000071`b85faa70 00007ff7`4915f677     : 00004f40`0440c128 00004f40`030c0140 00004f40`042d5ca0 00004f40`0440c120 : Signal!uv_fs_get_ptr+0x17d930
00000071`b85fab80 00007ff7`48a7ac95     : 00004f40`030c0090 00007ff7`48a79307 00000000`00010540 00007ff7`48a8431e : Signal!uv_fs_get_ptr+0x17d677
00000071`b85fac30 00007ff7`49157b5c     : 00000000`00000000 00007fff`b3b406df 00000000`00000000 00007ff7`46e685d9 : Signal!uv_fs_get_system_error+0x218595
00000071`b85fac90 00007ff7`49156895     : 00000000`00000000 00000000`00000000 00004f40`0049cf00 0000022f`dedf4d20 : Signal!uv_fs_get_ptr+0x175b5c
00000071`b85fad30 00007ff7`48d3ac1f     : 000009ad`b18a3e93 00007fff`b3b54810 00000000`00000000 00000000`00000036 : Signal!uv_fs_get_ptr+0x174895
00000071`b85fae70 00007ff7`48d3a5ef     : 00000000`00000000 00000000`00000086 0000e27f`5d027bf9 00000000`00000000 : Signal!GetHandleVerifier+0x17339f
00000071`b85faed0 00007fff`b3b3ef75     : 00000238`04ba5000 00000000`00000001 00000000`00000001 00000000`00010540 : Signal!GetHandleVerifier+0x172d6f

Screenshots

No response

Signal version

7.11.0

Operating system

Windows 10 (19045.4412)

Version of Signal on your phone

7.7.2

Link to debug log

https://debuglogs.org/desktop/7.11.0/e2aca21c9dfe86a098c76cd93d463c6ce8816cede3774e66ac3e34fb216c8734.gz

[ashemedai]

Some additional data:

• This is the second or third time now in ~2 weeks that this exact exception occurred.
• I have no newer version than 7.7.2 via Google's Play Store yet.
• After starting Signal after that exception it runs stable until a possible application restart.