0000700: Crash at map start for custom map (containing standard WoG objects) - MantisBT

MantisBT

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0000700

VCMI

Mechanics - Other

public

2011-03-04 02:24

2014-05-30 17:40

Reporter

Zamolxis

Assigned To

Warmonger

Priority

normal

Severity

crash

Reproducibility

always

Status

closed

Resolution

fixed

Platform

AMD 5600+

OS

Windows

OS Version

XP SP3

Product Version

0.84

Target Version

Fixed in Version

0.85

Summary

0000700: Crash at map start for custom map (containing standard WoG objects)

Description

Please see attached map, screenshot & logs (no crashdump created).

I made multiple additions to the map I've been using since 0000570, but when I tried to start it, I got the Runtime Error crash. I validated the map in the Editor and it opened under WoG. I also removed some of the more rare WoG objects, but the crash was still occurring. I couldn't check each and every object because I added at least 50, but I guess you have better tools to trace the cause.

Tags

No tags attached.

VCMI_Tests_2011.h3m [^] (18,615 bytes) 2011-03-04 02:24

2011-03-04_WoGMapCrash.jpg [^] (124,064 bytes) 2011-03-04 02:25

2011-03-04_WoGMapCrash.7z [^] (4,850 bytes) 2011-03-04 02:26

Relationships

Notes
(0001619) Ivan (developer) 2011-03-04 13:29	>>I couldn't check each and every object Crash located in hero placeholder loading. Check placeholder at underground, 55,25

(0001620) Zamolxis (viewer) 2011-03-04 13:54	It's that indeed. Just curious - where did you look to spot the cause? Did you use a debugging tool, or is it something I could have found myself if I looked in the right file?

(0001638) Warmonger (administrator) 2011-03-08 14:06	Don't know about Ivan, but indeed we have quite handy debugger built in MVS. Without it, it would be impossible to track most of bugs. The hero placeholder seems to be not handled. Crash was forced by coders who just didn't know what it is ;): int a = bufor[i++]; //unkown byte, seems to be always 0 (if not - scream!) assert(!a); I enabled it in r2026 as it doesn't seem to have negative influence on game.

(0001639) Tow dragon (viewer) 2011-03-08 17:55	I think that assertion was left there to see what that byte means. Maybe it contains important information?

Issue History
Date Modified	Username	Field	Change
2011-03-04 02:24	Zamolxis	New Issue
2011-03-04 02:24	Zamolxis	File Added: VCMI_Tests_2011.h3m
2011-03-04 02:25	Zamolxis	File Added: 2011-03-04_WoGMapCrash.jpg
2011-03-04 02:26	Zamolxis	File Added: 2011-03-04_WoGMapCrash.7z
2011-03-04 13:29	Ivan	Note Added: 0001619
2011-03-04 13:54	Zamolxis	Note Added: 0001620
2011-03-08 14:06	Warmonger	Note Added: 0001638
2011-03-08 14:06	Warmonger	Status	new => resolved
2011-03-08 14:06	Warmonger	Fixed in Version	=> 0.89
2011-03-08 14:06	Warmonger	Resolution	open => fixed
2011-03-08 14:06	Warmonger	Assigned To	=> Warmonger
2011-03-08 17:55	Tow dragon	Note Added: 0001639
2014-05-30 17:40	beegee	Status	resolved => closed

Site | Forums | Wiki | Slack | GitHub

Copyright © 2000 - 2024 MantisBT Team