Jamie Kyle

@mfc Can you share a debuglog? https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports

Can you include a debuglogs with your report: https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports

Looking through your log, this is all typical network connection timeout issues. Do you know which version it stopped working for you? I'd recommend reviewing all of your network and...

@avi12 So are you not able to get the app to crash again?

There is info on a crash that happened in your debuglog: ``` "crash_info": { "address": "0x00007ff7493d1c1f", "adjusted_address": null, "assertion": null, "crashing_thread": 0, "instruction": null, "memory_accesses": null, "possible_bit_flips": null, "type": "EXCEPTION_BREAKPOINT"...

Can you submit the debuglog?

It looks like its the same GPU issue: ``` 6: static void content::`anonymous namespace'::IntentionallyCrashBrowserForUnusableGpuProcess()+0x2d (gpu_data_manager_impl_private.cc:436) 17: content::GpuDataManagerImplPrivate::FallBackToNextGpuMode()+0x38 ``` You may just want to run Signal with `--disable-gpu` all the time...

It's not likely something that we can fix in Signal, it's likely a problem with Chromium or Electron, probably related to your hardware or some sort of configuration. There are...

Sorry about that, please let us know if the `--disable-gpu` workaround doesn't end up working out

@fdutheil We do rely on the format that windows tells us that the device is using, and have some code to convert multi-channel input to a single channel, which I...