Minor bug - Can't open Sequencer due to video limitation, no warning message (resolved)

[k6ccc]

This one is a minor one.  One of the computers I have LOR loaded on is my file server.  It is used to run the year round landscape lighting show.  Remember we're talking about a file server.  It does not meet the Open GL requirements for S5 or S6, but the show player runs fine, so that is not a limitation.

In S5, if you opened Sequencer, it would pop up a warning that the computer did not meet the video requirement advising that you would be unable to open any sequences.  In both 6.1.2 and 6.1.8, that warning is not there and it will try to open a sequence.  However during the loading process, Sequencer will simply crash with no warning or error message.

Light-O-Rama S6 Control Panel (64-bit)
Version 6.1.8
Copyright 2022 Light-O-Rama, Inc.
Pro Edition
Registered to: Jim Walls

Microsoft Windows Server 2019 Essentials 64-bit
Intel® Xeon® CPU   L5520 @ 2.27GHz
Microsoft Basic Display Adapter

 

The Windows Application event log showed these three log entries before I upgraded to 6.1.8 - similar errors on 6.1.8 (first two are errors and the third is Information):

Quote

Application: LORSequencer.exe
CoreCLR Version: 6.0.922.41905
.NET Version: 6.0.9
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFA5177216B (00007FFA515A0000) with exit code c0000005.

Quote

Faulting application name: LORSequencer.exe, version: 6.1.0.2, time stamp: 0x62b2fac5
Faulting module name: coreclr.dll, version: 6.0.922.41905, time stamp: 0x62ffe9cf
Exception code: 0xc0000005
Fault offset: 0x00000000001d216b
Faulting process id: 0x21cc
Faulting application start time: 0x01d9189b09e029ed
Faulting application path: C:\Program Files (x86)\Light-O-Rama\LORSequencer.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.9\coreclr.dll
Report Id: 71cde3f5-238b-4885-b017-226e334ef3e7
Faulting package full name:
Faulting package-relative application ID:

Quote

Fault bucket 1706414254982895101, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: LORSequencer.exe
P2: 6.1.0.2
P3: 62b2fac5
P4: coreclr.dll
P5: 6.0.922.41905
P6: 62ffe9cf
P7: c0000005
P8: 00000000001d216b
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER270D.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FA9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FCA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FC8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FE8.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LORSequencer.exe_ec5b4f81be1d3d565b9ca4c6a28a011c295c07d_fcd0e0b6_0f6a313f

Analysis symbol:
Rechecking for solution: 0
Report Id: 71cde3f5-238b-4885-b017-226e334ef3e7
Report Status: 268435456
Hashed bucket: 2e6ee9b612b0aa65a7ae66b953eb15fd
Cab Guid: 0

 

Edited December 25, 2022 by k6ccc

[MattBrown]

This should be fixed in the next release.

[k6ccc]

Confirmed fixed in 6.1.10

Thanks Matt.