View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002848||3 - Current Dev List||Bug||public||2018-08-22 19:06||2018-08-22 19:08|
|Priority||normal||Severity||crash||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0002848: Digital Master: crashes when logging from sound processing thread|
No repro, since this is a set of dumps that I picked up from the Dev Dashboard.
The sound background processing thread is ending up at abort() to shut down the application after a call to Log().Add() to log a string. From the disassembly, I can see that the call to Log().Add() is made at both call stacks, leaving the return address one layer down in the reported stack. However, I can't figure out how (or for what cause) a call to Log().Add() would result in a call to abort().
Perhaps there's another layer of fast failure handling inbetween and that's causing me to miss the call.
Reports found for 843 and 876. One spreadsheet is attached from each build with a populated stack.
|Tags||No tags attached.|