20-30 second Crash to Desktop

[HightowerMD11]

Hello everyone.

I am trying to troubleshoot a new latest version OpenCPN installation that quickly results in a CTD. (20-30seconds) . There is a message but it was so fast, I had to take a video of the desktop and reduce the speed to see it. But all it says is OpenCPN has stopped responding, with a resulting memory dump message but with no other details.

I have gone through alot of forum threads and have done alot of recommended steps but to no avail.

1)Wiped out .ini file
2))completely wiped out the programdata\opencpn
3)complete uninstall, with a revoinstaller to remove any registry entries (there were none)
4) Safe mode startup (still crashes)
5) )no charts are installed
6) plugins disabled - even default and no other plugins installed
7) open gl disabled
8) ensured no interference from AV. Has a folder exception.
9) .log file does not reveal anything suspicious other than a watchdog timeout but only seen it once or twice. Other times its not there.
10) Ran it as administrator.
11) Solution on these forums to start with .bat file did not work.

Its difficult to get into settings and change or test things around because of the quick crash. I suspect editing the .ini file is the only way around it.

I have no physical GPS to connect to. I want to use it with simulation software that spits out NMEA data. But I doubt that OCPN would crash without having live position data.

Fairly new clean windows 11 install (4 months ago)
64gb ram (not a RAM issue.)
GPU drivers up to date

Want to try an archived version but cannot find download links for them.

Tried to attach .ini and .log files but attachment prompt says they are invalid for some reason.

I am at a loss. Any insight would be appreciated.

Thank you

[PippaB]

I can't offer much, but to attach .ini and .log, change/add the file extension to .pdf (usually xxx.ini.pdf and xxx.log.pdf). This gets past the forum filetype check (it only uses the final extension) and pretty much everyone here working with these knows to download and remove the .pdf to assist.

[bdbcat]

MD11...
As always, archive versions for Windows and Mac are available here:
https://github.com/OpenCPN/OpenCPN/releases


Good Luck
Dave

[barnakiel]

Have you checked the installation file (size, checksum ?)


Perhaps the file from which you install is corrupt (while downloading, e.g.)


b.

[HightowerMD11]

Originally Posted by bdbcat

MD11...
As always, archive versions for Windows and Mac are available here:
https://github.com/OpenCPN/OpenCPN/releases


Good Luck
Dave

Hi Dave

Thanks. I tried, but on every archive it states
For Download links, plugins, documentation, and other useful information, visit our support website at:
https://opencpn.org/""

On the official site I only see the link for the latest version.

[HightowerMD11]

Originally Posted by barnakiel

Have you checked the installation file (size, checksum ?)


Perhaps the file from which you install is corrupt (while downloading, e.g.)


b.

Yes Checksum matches. Thanks for the input

[HightowerMD11]

.log and .ini files now attached.

Thanks

[HightowerMD11]

Do you have a direct link to archived older versions to try? The github older versions refer to opencpn.org to download and clicking on downloads and archived versions links back to github.

[bdbcat]

MD11...
https://github.com/OpenCPN/OpenCPN/releases


Click on "Assets" for any particular release.
Good Luck
Dave

[janp391]

I had a similar problem
I installed an older version (5.8.2). When it was running I zoomed out (-)and then inactivated the OpenGL. Then try the new version and check that OpenGL is unchecked. Maybe this will help you

[HightowerMD11]

Ok 5.10.2 installed and does not crash, but with nothing extra installed, it is extremely slow and unresponsive from one click anywhere. (settings, anywhere on map) then revives and process repeats. deleteing .ini again and same thing. Now installed 5.12.4 and back to crashing in 20sec. At least that part has been troubleshooted. OpenGL on or off makes no difference.
Thanks for the help. Will continue working on it.

[Shrew]

There are two partitions in a Windows OS The System partition (Operating System) and the User/Application partition (Applications).

A System crash (Kernel Dump) leads to a blue screen Blue Screen of Death (BSOD)

An Application crash (User Mode Process Dump) is simply the application process that crashes. Which is what I suspect you're calling a Crash To Desktop (With it's own TLA (CTD). I have never heard called that in 25+ yrs in the enterprise software space........ but it's accurate).

When a process crashes, it dumps the entirety of its process in memory into a crash/dump file.

1) Logon to the Windows host where you want to configure to capture user-mode process dumps

2) Open the Windows Registry

Start -> Run -> Regedit

3) Browse to the following registry hive:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Wind ows Error Reporting\LocalDumps

4) Create the following keys:

KeyName: DumpFolder
Data Type: REG_EXPAND_SZ
Value: %LOCALAPPDATA%\CrashDumps

KeyName: DumpCount
Data Type: REG_DWORD
Value: 3

KeyName: DumpType
Data type: REG_DWORD
Value: 2

Data Values:
0 = Create a custom dump
1 = Mini dump
2 = Full dump

Set the dump count to 1 to only retain one dump file and overwrite that dump with each subsequent dump.

You should be able to share the dump file with the developer to understand the root cause of the dump.

[wholybee]

I would hesitate on trying to capture a dump unless the developer requests it. Especially since one of the lead developers is in this thread. Often they are useless without running a debug build.

According to the log, OpenCPN crashes when the GPS timeout is reached. That might be a hint, maybe OpenCPN is trying to use a GPS that isn't there?

I might be wrong, but I think recent versions of OCPN can connect to a GPS through a Windows API. (bdcat could confirm)
Open Windows Settings -> Privacy & Security -> Location

From there you can turn on/off location settings. Toggle that and see if it helps.

[Shrew]

Originally Posted by wholybee

Often they are useless without running a debug build.

As someone who gathers and reads them daily, I would say this is inaccurate information. Certainly useless if you don't know how to read them. The only reason for an instrumented build if the unhandled exception occurs in a section of code that is used in multiple places. In that case, you might need to notate each section so you can determine which section is actually crashing.

As someone who deals with process crashes daily, this is really step #1.