MantisBT - VCMI
View Issue Details
0002801VCMIGUI - Adventure Mappublic2017-10-03 17:562024-02-05 21:34
Dydzio 
Warmonger 
normalcrashalways
closedfixed 
Microsoft WindowsWindows 7Home Premium x64
1.next 
 
0002801: Crash with MSVS 2015 debug build
Crash happens after building debug version of VCMI in Visual Studio 2015 and running it (assert failed). Crash appears after launching a scenario and passing a turn (tested on "arrogance" map).
1. Start some singleplayer scenario (tested on "arrogance")
2. Pass new turn, maybe you need to "play properly" before that (move a hero, leave some path for next turn available - crash seems to be in pathfinder)
No tags attached.
Issue History
2017-10-03 17:56DydzioNew Issue
2017-10-03 18:30AVSNote Added: 0007287
2017-10-03 19:35DydzioNote Added: 0007288
2017-10-03 20:00DydzioNote Edited: 0007288bug_revision_view_page.php?bugnote_id=7288#r3406
2017-11-04 07:43WarmongerNote Added: 0007315
2017-11-04 07:43WarmongerAssigned To => Warmonger
2017-11-04 07:43WarmongerStatusnew => confirmed
2017-11-04 09:41WarmongerNote Edited: 0007315bug_revision_view_page.php?bugnote_id=7315#r3408
2018-03-31 11:08CzesiekNote Added: 0007554
2022-04-03 13:20PovelitelNote Added: 0008261
2022-09-04 20:03WarmongerNote Added: 0008323
2023-04-12 16:59IvanStatusconfirmed => acknowledged
2024-02-05 21:34IvanStatusacknowledged => closed
2024-02-05 21:34IvanResolutionopen => fixed

Notes
(0007287)
AVS   
2017-10-03 18:30   
Please attach assert error message and backtrace if possible.
(0007288)
Dydzio   
2017-10-03 19:35   
(edited on: 2017-10-03 20:00)
Screenshot: http://ctrlv.in/1010539 [^]

Backtrace: https://gist.github.com/dydzio0614/6b17d8cd3f90f65f0cda319578d8934f [^]

Problem may be related to violation of strict weak ordering somewhere in code.

(0007315)
Warmonger   
2017-11-04 07:43   
(edited on: 2017-11-04 09:41)
I confirm the issue. Invalid heap inside pop() method indeed might be build / library / package problem, no other ideas.

(0007554)
Czesiek   
2018-03-31 11:08   
I also confirm the issue. Debug 64 bit on MSVS 2015
(0008261)
Povelitel   
2022-04-03 13:20   
For the sake of interest, I ask, is this still reproduced in the 2022 studio?
(0008323)
Warmonger   
2022-09-04 20:03   
I just uninstalled MSVS 2019 yesterday and plan to work with 2022 from now on. There's no point in trying to reproduce the issue with a legacy IDE.

So it's a candidate for closing.