Loading a scenario totally crashes computer

[chrispman]

Attempting to load a scenario in the editor, the progress bar advances a few steps, then stops.

The computer is completely unresponsive, it takes minutes for the task manager to open. Command process is at 100%.

Steam version, Build 1299.1. NVidia overlay disabled.

I have attached the exception log.

On the third attempt (after reboot) it worked, so I can't really investigate any further.

[Deserere]

Hi chrispman, can we have a copy of the scenario you were loading?
Thanks

[chrispman]

I have updated it to the current database version in the meantime, which, I must admit, was not an act of cleverness on my part with regards to debugging...

[BDukes]

Just happened with the attached scenario.

Nothing in the windows or exception logs. Computer does seem to spool up considerably.

M

[Quark73]

Had the same,
was trying to load Dodging the Bullit from Strike Tutorials in Mission Editor. Windows 11, Nvidia share switched off. Was a major cluster f*ck. Took three to five restarts to fix the system.

edit: Ehm, using the steam version. And steam was trying hard to update afterwards.

[Shkval25]

I have had the exact same issue, including system freeze and 100% CPU, on a non-Steam install of 1299.1. Exception log and scenario enclosed.

[SteveMcClaire]

If you have encountered the 'crash while loading scenario' error in recent Command beta builds and are willing to help with an experiment to try and pinpoint the cause, please try the following:

Before you load a scenario in Commad, please check Windows Task Manager (right click the Windows task bar and select 'Task Manager') to see if you have multiple instances of Command running on your machine. You should only see Command listed under the 'Apps' section of Task Manager.

If you see 'Command (32 bit)' under both Apps and Background Processes, right click the entry listed under Background Processes and select 'End Task' to kill it.

If Task Manager only showed 'Command (32 bit)' under the 'Apps' section, or you ended the task that was shown under 'Background Processes,' and you still see a crash loading a scenario, please post the information here. This will help confirm if it is due to a previous instance of Command being 'stuck' running in the background.

[BDukes]

Hi Steve

Doesn't happen the first time a load a scenario for the day. Does happen if I open multiple scenarios, close CMO, and start the scenario above. This doesn't happen all the time but is frequent. I did capture a task manager shot prior to a crash.

TaskManager.JPG (142.26 KiB) Viewed 1193 times

[SteveMcClaire]

I did capture a task manager shot prior to a crash.

Hi BDukes -- did the original screenshot extend any further down the Task Manager list? The section of interest is 'Background Processes' which appear below 'Apps' in the Task Manager list.

[thewood1]

On the Stest scenario, it only has 3 airfields as collected groups. On start at double flame, the CPU usage goes to 90%. If I delete all units, it jumps to 99%. If I change the db, it drops back to low CPU usage. Seems like there is something inherent in that scenario or in 497a db thats causing the issue.

[BDukes]

I did capture a task manager shot prior to a crash.

Hi BDukes -- did the original screenshot extend any further down the Task Manager list? The section of interest is 'Background Processes' which appear below 'Apps' in the Task Manager list.

Hi

Yeah just created the crash again and took another screenshot. Sure did there are 105 processes. The screenshot below is prior to the crash. I extended down, guessing you're looking for another command instance. I don't see it.

Taskmanager.JPG (108.63 KiB) Viewed 1164 times

[BDukes]

Nothing in my Windows Logs (any of them). No entry is close the time it started.

These are in the CMO Logging. Time is close but not sure:

12/15/2022 12:48:33 PM -- B1299.1 -- Object reference not set to an instance of an object.
Exception: Object reference not set to an instance of an object.
Stack Trace: at System.Collections.Generic.HashSet`1.AddIfNotPresent(T value)
at Command_Core.ActiveUnit.set_IsAutoDetectable(Side SideAttemptingDetection, Boolean value)
at Command_Core.Facility.VitIfTjO6aDmvkFfyYf6(Object , Object , Boolean value)
at Command_Core.Facility.xUNYCT7fQJU(XmlNode& , ConcurrentDictionary`2& , Scenario& , Boolean )
Call Stack & Error details:
Error at 100541,


12/15/2022 12:48:33 PM -- B1299.1 -- Object reference not set to an instance of an object.
Exception: Object reference not set to an instance of an object.
Stack Trace: at System.Collections.Generic.HashSet`1.AddIfNotPresent(T value)
at Command_Core.ActiveUnit.set_IsAutoDetectable(Side SideAttemptingDetection, Boolean value)
at Command_Core.Facility.VitIfTjO6aDmvkFfyYf6(Object , Object , Boolean value)
at Command_Core.Facility.xUNYCT7fQJU(XmlNode& , ConcurrentDictionary`2& , Scenario& , Boolean )
Call Stack & Error details:
Error at 100541,

[SteveMcClaire]

Yeah just created the crash again and took another screenshot.

Well, RIP that theory. Thanks though!

[BDukes]

No problem. Good luck with this one.

M

[ThunderCBR]

I've been having the same issue with one additional issue. I've had to do a hard reset of the computer due to the aforementioned CPU spike. When I reload the scenario, it loads but the file is completely corrupted and I'm missing a lot of content, bases have went to a single runway (all other base units disappeared), aircraft disappear, etc. I'm a idiot and didn't create a backup of my scenario file and I've lost a bunch of work.

This is on the Steam version 1299.1. I looked on the task manager and I see two entries in the dropdown under CMO.

[ThunderCBR]

Just happened again, and it generated a massive exception log file. Hopefully this helps.

[SteveMcClaire]

When I reload the scenario, it loads but the file is completely corrupted and I'm missing a lot of content, bases have went to a single runway (all other base units disappeared), aircraft disappear, etc.er CMO.

Can you provide the scenario file please? Loading a scenario should not corrupt the file on disk.

I looked on the task manager and I see two entries in the dropdown under CMO.

You may see several entires for Command under the 'Apps' section of Windows Task Manager. If you see an instance of Command (32 bit) under the 'Background Processes' section of Task Manager, then you have an instance of Command 'stuck' in memory. Close down that background process.

[ThunderCBR]

Interestingly enough I just reload the supposed corrupted scenario and it loaded just fine today. Totally odd... I could swear when I reloaded after a hard lock up the other day that it appeared 'corrupted'. No idea what happened there. If I see it happen again I'll immediately zip up the scen file and log and post here. Don't want you chasing ghosts.

[BDukes]

Steve. Crashed tonight but not the whole computer. Windows logging seems to have caught some information

Log Name: Application
Source: Windows Error Reporting
Date: 12/20/2022 6:02:49 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: DESKTOP-191BQK9\myky9
Computer: DESKTOP-191BQK9
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Command.exe
P2: 1.0.0.0
P3: 63a1f893
P4: b972
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\Users\myky9\AppData\Local\Temp\WER.c7063a80-c95a-4934-b2a6-40ee516f09cc.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.891186aa-1cbe-4d61-b405-3021774e757f.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20221218_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5fd1132f-02ef-4dea-a955-f36e4de745dc.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6ffdd456-03c1-439c-a8bd-c7d4346d6100.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.59390093-fedb-4e14-96ce-73fa9c8405a4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.87c2514a-47eb-4794-b358-5c3a1cbb4446.tmp.txt
\\?\C:\Users\myky9\AppData\Local\Temp\WER.5582348b-ef47-4e59-b764-9ddd820a6286.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2e4d17f9-68a7-43c9-a773-ce075131d3b6.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.18f03423-7ee8-4457-ab77-b36a85ce7508.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef\memory.hdmp
\\?\C:\Users\myky9\AppData\Local\Temp\WER.e662e032-e4b5-42c1-ba5c-7f8ddcc24fbf.tmp.WERDataCollectionStatus.txt
WERGenerationLog.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef

Analysis symbol:
Rechecking for solution: 0
Report Id: 7835aec2-dd76-49fe-8ca0-3dd90e92fabc
Report Status: 4
Hashed bucket:
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2022-12-20T23:02:49.0110975Z" />
<EventRecordID>10949</EventRecordID>
<Correlation />
<Execution ProcessID="29916" ThreadID="24420" />
<Channel>Application</Channel>
<Computer>DESKTOP-191BQK9</Computer>
<Security UserID="S-1-5-21-3926811821-2534079915-2241057899-1001" />
</System>
<EventData>
<Data Name="Bucket">
</Data>
<Data Name="BucketType">0</Data>
<Data Name="EventName">AppHangB1</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">Command.exe</Data>
<Data Name="P2">1.0.0.0</Data>
<Data Name="P3">63a1f893</Data>
<Data Name="P4">b972</Data>
<Data Name="P5">67246080</Data>
<Data Name="P6">
</Data>
<Data Name="P7">
</Data>
<Data Name="P8">
</Data>
<Data Name="P9">
</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\\?\C:\Users\myky9\AppData\Local\Temp\WER.c7063a80-c95a-4934-b2a6-40ee516f09cc.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.891186aa-1cbe-4d61-b405-3021774e757f.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20221218_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5fd1132f-02ef-4dea-a955-f36e4de745dc.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6ffdd456-03c1-439c-a8bd-c7d4346d6100.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.59390093-fedb-4e14-96ce-73fa9c8405a4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.87c2514a-47eb-4794-b358-5c3a1cbb4446.tmp.txt
\\?\C:\Users\myky9\AppData\Local\Temp\WER.5582348b-ef47-4e59-b764-9ddd820a6286.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2e4d17f9-68a7-43c9-a773-ce075131d3b6.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.18f03423-7ee8-4457-ab77-b36a85ce7508.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef\memory.hdmp
\\?\C:\Users\myky9\AppData\Local\Temp\WER.e662e032-e4b5-42c1-ba5c-7f8ddcc24fbf.tmp.WERDataCollectionStatus.txt
WERGenerationLog.txt</Data>
<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Command.exe_1e95e768cbacef62af38369365c49a85cac5eb6f_8228e01f_cab_1fd116d9-cbdf-4c7e-bd24-e83b96c64fef</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">7835aec2-dd76-49fe-8ca0-3dd90e92fabc</Data>
<Data Name="ReportStatus">4</Data>
<Data Name="HashedBucket">
</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>

[BDukes]

Fixed.

See this post

https://www.matrixgames.com/forums/view ... 0&t=391475