Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Bryan See on January 20, 2017, 06:53:30 am

Title: Crash on mission load
Post by: Bryan See on January 20, 2017, 06:53:30 am: Hello, I've been trying out nightly builds for more than three years.

However, upon loading my mission for a test on FSO's new particle system, it crashes. Apparently, there's an invalid index 0 in "index >= 0 && index < numHats()" at joy-sdl.cpp, line 445.

Attached is the fs2_open.log file.

EDIT: I think the Avast is the culprit, as it messed all of its executables and dll files, I've excluded it from its file system scan. But, is there a need to make it the AV think it's free of something bad (malware, backdoors, etc.).

EDIT #2: Still, it doesn't solve the problem.

Code: [Select]
Assert: "index >= 0 && index < numHats()" File: joy-sdl.cpp Line: 445 Invalid index 0! ntdll.dll! NtWaitForSingleObject + 20 bytes KERNELBASE.dll! WaitForSingleObjectEx + 143 bytes fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> KERNEL32.DLL! BaseThreadInitThunk + 20 bytes ntdll.dll! RtlUserThreadStart + 33 bytes [ This info is in the clipboard so you can paste it somewhere now ] Use Debug to break into Debugger, Exit will close the application. ntdll.dll! NtWaitForSingleObject + 20 bytes KERNELBASE.dll! WaitForSingleObjectEx + 143 bytes fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol> KERNEL32.DLL! BaseThreadInitThunk + 20 bytes ntdll.dll! RtlUserThreadStart + 33 bytes
[attachment deleted by admin]
Title: Re: Crash on mission load
Post by: m!m on January 20, 2017, 12:04:05 pm: The E has found a fix for this and it has been merged. The next nightly should fix this issue.
Title: Re: Crash on mission load
Post by: Bryan See on January 20, 2017, 12:20:46 pm: Quote from: m!m on January 20, 2017, 12:04:05 pm
The E has found a fix for this and it has been merged. The next nightly should fix this issue.
And when was it happened? And when the next nightly build released, fixing this persistent one?
Title: Re: Crash on mission load
Post by: m!m on January 20, 2017, 12:23:44 pm: The next nightly will be built tomorrow. Typically they appear around one day after the last build.
Title: Re: Crash on mission load
Post by: Bryan See on January 20, 2017, 12:31:58 pm: But I want that thing fixed by then. If not, we'll likely not be able to playtest missions with each new nightly build.
Title: Re: Crash on mission load
Post by: m!m on January 20, 2017, 12:34:54 pm: It has already been fixed. It will just take a while until the next nightly build will be released which contains the fix.
Title: Re: Crash on mission load
Post by: Bryan See on January 20, 2017, 12:38:21 pm: Okay, noted.
Title: Re: Crash on mission load
Post by: Bryan See on January 21, 2017, 09:00:21 am: Downloaded the latest nightly build and run it. I was able to load a mission without any crash. Thanks a lot :D