Warzone 2100 appcrash

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
Stuns
New user
Posts: 1
Joined: 25 May 2013, 13:28

Warzone 2100 appcrash

Post by Stuns »

:annoyed:

I played the map 8c-Mero_Star in singleplayermode against bots when suddenly everything froze before a message popped up which said; Warzone 2100 crashed, check logs for more information <- or something

An appcrash isn't that frustrating, but I lost 40min progress so I hope it isn't going to happen again.

Why did it crash and how to fix it?

Here are the logs:

-------------------

Code: Select all

Error occured on Saturday, May 25, 2013 at 13:24:23.

Program: C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe(warzone2100)
Command line: "C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe" 
Version: Version 3.1.0 - Built Jan 14 2013
Distributor: wz2100.net
Compiled on: Jan 14 2013 20:42:51
Compiled by: GCC 4.7.0
Compiled mode: Release build
Executed on: Sat May 25 12:28:24 2013

Pointers: 32bit

Compiled against PhysicsFS version: 2.0.3
Running with PhysicsFS version: 2.0.3

Misc Data:
[12:28:24]Video Mode 1920 x 1080 (fullscreen)
[12:28:24]OpenGL Vendor: ATI Technologies Inc.
[12:28:24]OpenGL Renderer: Radeon X1950 Series 
[12:28:24]OpenGL Version: 2.0.6479 Release
[12:28:24]GLEW Version: 1.7.0
[12:28:24]OpenGL GLSL Version : 1.10
[12:28:26]OpenAL Device Name: DirectSound Default
[12:28:26]OpenAL Vendor: OpenAL Community
[12:28:26]OpenAL Version: 1.1 ALSOFT 1.13
[12:28:26]OpenAL Renderer: OpenAL Soft
[12:28:26]OpenAL Extensions: AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_LOKI_quadriphonic AL_SOFT_buffer_sub_data AL_SOFT_loop_points
[12:28:26]Using Backend: SDL
[12:28:26]Using language: Systemsprache
[12:32:59]Current Level/map is Mero_Star-T1


C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe caused an Access Violation at location 00b40c6e in module C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe Reading from location 00000f90.

Log message: info    |01:19:20: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: '27 (CALL_STRUCT_ATTACKED)'
Log message: info    |01:19:21: [structSetManufacture:993] Wrong template for player 6 factory, type 16.
Log message: info    |01:19:21: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:19:41: [structSetManufacture:993] Wrong template for player 6 factory, type 17.
Log message: info    |01:19:41: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:19:41: [structSetManufacture:993] Wrong template for player 6 factory, type 17.
Log message: info    |01:19:41: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:19:41: [structSetManufacture:993] Wrong template for player 7 factory, type 17.
Log message: info    |01:19:41: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:19:41: [structSetManufacture:993] Wrong template for player 7 factory, type 17.
Log message: info    |01:19:41: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:19:41: [structSetManufacture:993] Wrong template for player 7 factory, type 17.
Log message: info    |01:19:41: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: error   |01:20:40: [buildFeature:283] Artefakt(166999) already placed at (184+1, 139+1) when trying to place Artefakt(168551) at (184+1, 139+1) - removing it
Log message: info    |01:21:32: [structSetManufacture:993] Wrong template for player 7 factory, type 16.
Log message: info    |01:21:32: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:22:49: [structSetManufacture:993] Wrong template for player 6 factory, type 16.
Log message: info    |01:22:49: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'
Log message: info    |01:22:51: [structSetManufacture:993] Wrong template for player 6 factory, type 1.
Log message: info    |01:22:51: [structSetManufacture:993] Assert in Warzone: structure.cpp:993 (!psTempl || (validTemplateForFactory(psTempl, psStruct) && researchedTemplate(psTempl, psStruct->player, true)) || psStruct->player == scavengerPlayer() || !bMultiPlayer), last script event: 'N/A'

Registers:
eax=00000f90 ebx=00000020 ecx=0bf4fc48 edx=00000020 esi=06fa9b08 edi=00458c40
eip=00b40c6e esp=0bf4fc24 ebp=0bf4fc28 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206

Call stack:
00B40C6E  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:00B40C6E  std::_Bit_reference::operator bool  /opt/mxe/usr/bin/../lib/gcc/i686-pc-mingw32/4.7.0/include/c++/bits/stl_bvector.h:82
00B41704  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:00B41704  std::_Bit_const_iterator::operator*  /opt/mxe/usr/bin/../lib/gcc/i686-pc-mingw32/4.7.0/include/c++/bits/stl_bvector.h:288
00B45C9F  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:00B45C9F  std::vector<bool, std::allocator<bool> >::operator[]  /opt/mxe/usr/bin/../lib/gcc/i686-pc-mingw32/4.7.0/include/c++/bits/stl_bvector.h:713
00B31098  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:00B31098  PathfindContext::isBlocked  /warzone2100/src/astar.cpp:144
0040D73D  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:0040D73D  fpathAStarExplore  /warzone2100/src/astar.cpp:400
0040DBF3  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:0040DBF3  fpathAStarRoute  /warzone2100/src/astar.cpp:482
0045A40E  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:0045A40E  fpathExecute  /warzone2100/src/fpath.cpp:513
00458E0E  C:\Program Files\Warzone 2100-3.1.0\warzone2100.exe:00458E0E  fpathThreadFunc  /warzone2100/src/fpath.cpp:104
Last edited by Staff on 26 May 2013, 03:34, edited 1 time in total.
Reason: add code tags
User avatar
Staff
Global Moderator
Global Moderator
Posts: 387
Joined: 27 May 2011, 04:08

Re: Warzone 2100 appcrash

Post by Staff »

You have run into the #1 bug that we can't fix, since we can't replicate it.
If you know how to replicate that exact crash, let us know in the bug tracker. http://developer.wz2100.net/newticket

Thanks!
Sorry, this account has been deactivated.
Please post issues in Website feedback instead, only Moderators can read things there.