Bug / Crash Exception Code 0xc0000409 - Printable Version +- Obi Official Forum (https://obi.virtualmethodstudio.com/forum) +-- Forum: Obi Users Category (https://obi.virtualmethodstudio.com/forum/forum-1.html) +--- Forum: Obi Fluid (https://obi.virtualmethodstudio.com/forum/forum-3.html) +--- Thread: Bug / Crash Exception Code 0xc0000409 (/thread-573.html) |
Exception Code 0xc0000409 - johnnychang - 02-05-2018 HI,My app has crashed.This application is a fluid, published using Unity3D. Here is the log from Windows' Event Viewer: Faulting application name: water.exe, version: 5.6.1.24755, time stamp: 0x5910657a Faulting module name: libOni.dll, version: 0.0.0.0, time stamp: 0x59a32a1d Exception code: 0xc0000409 Fault offset: 0x0006b926 Faulting process id: 0x41e8 Faulting application start time: 0x01d3e1bd5ddb1cfe Faulting application path: C:\Users\Administrator\Desktop\water1645\water.exe Faulting module path: C:\Users\Administrator\Desktop\water1645\water_Data\Plugins\libOni.dll Report Id: 35857696-b35c-4a2c-b6b5-b6bfacf2aad0 Faulting package full name: Faulting package-relative application ID: RE: Exception Code 0xc0000409 - josemendez - 02-05-2018 (02-05-2018, 08:32 AM)johnnychang Wrote: HI,My app has crashed.This application is a fluid, published using Unity3D. Hi johnny, Can you provide the full crash log, and ideally a stack trace? this report is pretty much useless on its own. Also, what Obi, Unity and Windows versions are you using? RE: Exception Code 0xc0000409 - johnnychang - 02-05-2018 (02-05-2018, 08:57 AM)josemendez Wrote: Hi johnny, I use ObiFluid 3.2, and the engine is Unity3D 5.6.1f1. This is all the crash logs , there is no such problem in the development mode & no stack trace information is generated,so I can't provide a full stack trace. (02-05-2018, 08:57 AM)josemendez Wrote: Hi johnny, My OS is Windows 10,system type is x64. RE: Exception Code 0xc0000409 - josemendez - 02-05-2018 (02-05-2018, 09:09 AM)johnnychang Wrote: I use ObiFluid 3.2, and the engine is Unity3D 5.6.1f1. Hi, Try upgrading to 3.4 (it is free) as several stability issues were addressed in 3.3 and 3.4. It may (or may not) solve the issue, but at least we make sure it is not happening due to a closed bug. cheers, |