PDA

View Full Version : FGU Crashing for Players



rocketvaultgames
January 23rd, 2024, 14:31
We've seen some issues in the past few weeks where the player's instances of FGU are crashing.

Sometimes a few players at once, sometimes a single player. Never the GM.

They all tell me an error message pops up but disappears before they can get any info from it.

Is there a place where this error message might be saved?

Trenloe
January 23rd, 2024, 14:35
<FG app data>\console.log

But it resets the next time FG is started - however there is a backup, but it will only have the data from FG when the issue occurred the first time FG is started.

Use option #1 from this Wiki page to collect the logs the first time FG is started after the crash: https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1242136781/How+to+Compile+Logs

Unfortunately, if it's a crash due to pushing machine resources, it may not show up in these logs. But, it's definitely the first place to look. And if they are Windows PCs crashing, look in the Windows Application log for possible crash errors.

Trenloe
January 23rd, 2024, 14:38
Also, as mentioned in your thread regarding momentary freezes - if you're sharing some of the large images you had with players with lower spec computers, that could well be causing them issues as well. As you have a pretty high spec computer, large images might appear to work OK for you but could cause issues for players with lower spec computers.

rocketvaultgames
January 23rd, 2024, 14:44
I'm not seeing any errors either before or after the crash in the logs.

Is there any way it is somehow a Unity Engine or Windows error that wouldn't be shown in the logs.

To be clear I am using extensions, so I'm not saying the crashes are FGU's fault... I'm just trying to diagnose and I'm at a loss as to where to start as the crashes see to be somewhat at random and only once or twice in a 3 hour period.

Thank you for your help.

Trenloe
January 23rd, 2024, 14:48
If the FG logs don't show anything (which they may not if it's a crash due to resource issues or other system issues) then look in the Windows Application Event log at the time of the crash.

rocketvaultgames
January 23rd, 2024, 20:43
I was able to get this from one of my players. I will definitely look into it, but I just wanted to ask here in case you can point me in any direction as to what might be the cause/solution.

The players tell me that the crashes happen when they are mousewheel zooming around on maps.

Thanks much!

Log Name: Application
Source: Application Error
Date: 1/22/2024 6:43:38 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-MR22CHB
Description:
Faulting application name: FantasyGrounds.exe, version: 2022.3.6.59111, time stamp: 0x64bff355
Faulting module name: mono-2.0-bdwgc.dll, version: 0.0.0.0, time stamp: 0x649ef009
Exception code: 0xc0000005
Fault offset: 0x00000000004d84bc
Faulting process id: 0x9a0
Faulting application start time: 0x01da4d8ea7472c56
Faulting application path: C:\Program Files\SmiteWorks\Fantasy Grounds\FantasyGrounds.exe
Faulting module path: C:\Program Files\SmiteWorks\Fantasy Grounds\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll
Report Id: 7b856af9-d08a-4f7b-b6a5-1175eef9d670
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-01-23T00:43:38.4033998Z" />
<EventRecordID>28573</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-MR22CHB</Computer>
<Security />
</System>
<EventData>
<Data>FantasyGrounds.exe</Data>
<Data>2022.3.6.59111</Data>
<Data>64bff355</Data>
<Data>mono-2.0-bdwgc.dll</Data>
<Data>0.0.0.0</Data>
<Data>649ef009</Data>
<Data>c0000005</Data>
<Data>00000000004d84bc</Data>
<Data>9a0</Data>
<Data>01da4d8ea7472c56</Data>
<Data>C:\Program Files\SmiteWorks\Fantasy Grounds\FantasyGrounds.exe</Data>
<Data>C:\Program Files\SmiteWorks\Fantasy Grounds\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll</Data>
<Data>7b856af9-d08a-4f7b-b6a5-1175eef9d670</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

pindercarl
January 23rd, 2024, 20:54
I was able to get this from one of my players. I will definitely look into it, but I just wanted to ask here in case you can point me in any direction as to what might be the cause/solution.

The players tell me that the crashes happen when they are mousewheel zooming around on maps.

Thanks much!

Log Name: Application
Source: Application Error
Date: 1/22/2024 6:43:38 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-MR22CHB
Description:
Faulting application name: FantasyGrounds.exe, version: 2022.3.6.59111, time stamp: 0x64bff355
Faulting module name: mono-2.0-bdwgc.dll, version: 0.0.0.0, time stamp: 0x649ef009
Exception code: 0xc0000005
Fault offset: 0x00000000004d84bc
Faulting process id: 0x9a0
Faulting application start time: 0x01da4d8ea7472c56
Faulting application path: C:\Program Files\SmiteWorks\Fantasy Grounds\FantasyGrounds.exe
Faulting module path: C:\Program Files\SmiteWorks\Fantasy Grounds\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll
Report Id: 7b856af9-d08a-4f7b-b6a5-1175eef9d670
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-01-23T00:43:38.4033998Z" />
<EventRecordID>28573</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-MR22CHB</Computer>
<Security />
</System>
<EventData>
<Data>FantasyGrounds.exe</Data>
<Data>2022.3.6.59111</Data>
<Data>64bff355</Data>
<Data>mono-2.0-bdwgc.dll</Data>
<Data>0.0.0.0</Data>
<Data>649ef009</Data>
<Data>c0000005</Data>
<Data>00000000004d84bc</Data>
<Data>9a0</Data>
<Data>01da4d8ea7472c56</Data>
<Data>C:\Program Files\SmiteWorks\Fantasy Grounds\FantasyGrounds.exe</Data>
<Data>C:\Program Files\SmiteWorks\Fantasy Grounds\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll</Data>
<Data>7b856af9-d08a-4f7b-b6a5-1175eef9d670</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Is this for the campaign that you provided for https://www.fantasygrounds.com/forums/showthread.php?80082-FGU-Freezes-Briefly-Every-10-Seconds ? If so, can you point me to some images that have been causing issues? Thanks.

rocketvaultgames
January 23rd, 2024, 21:14
Is this for the campaign that you provided for https://www.fantasygrounds.com/forums/showthread.php?80082-FGU-Freezes-Briefly-Every-10-Seconds ? If so, can you point me to some images that have been causing issues? Thanks.

It is the same campaign. To be clear, I am using a lot of extensions and not trying to blame FGU or make a bunch of work for you. I would just like to see if I can target certain extensions or images or whatever as likely culprits.

We've seen player crashes on the following (I know some are larger than recommended), but we have been using some of these maps for a long time and the crashes are just in the last couple of months:

Sometimes it's 2 players at a time, often just 1. They all have reasonably spec'd machines with dedicated video cards (RTX2060 on the bottom end).


Map - Elturel in Avernus
Map - Avernus (By Nico Sovanna)
Map - Temple of the Morninglord
Grand Cemetery - Chapel
Grand Cemetery - Ossuary Level
Map - Tower of Ber Nolmien
High Hall Cathedral
High Hall Catacombs



Thanks for all you do!

LordEntrails
January 23rd, 2024, 21:25
System crashes I always look to two things first; memory usage & graphics drivers.

Make sure the systems are avoiding swap if possible and try updating or rolling back graphic drivers or using default driver settings.
Third is if anyone is playing with their BIOS and overclocking things is to revert those.