DICE PACKS BUNDLE
  1. #1

    Event 1000 Application Error on Windows 10 Pro 1903

    After installing windows version 1903 on 10/11/19. Fantasy grounds classic crashes during AFK times. Confirmed memory usage below 2 GB for fantasy grounds and total memory at about 8 GB of 16 GB. Running the same campaign with the same loaded modules and extensions for a month before 1903 update. Use Fantasy Grounds every day for game prep and when I leave the PC running FG or work on another window with FG in the background, FG crashes after minutes at idle. Coincidentally, there is a map open with a newly applied drawing or mask each time this occurs. Not having any issues with other software on this PC. Any recommendations?

    Error 10/14/2019 11:30:33 AM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: combase.dll, version: 10.0.18362.356, time stamp: 0x3c1d04fa
    Exception code: 0xc0000409
    Fault offset: 0x0016a1fe
    Faulting process id: 0x481c
    Faulting application start time: 0x01d582a3d487b72b
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\WINDOWS\System32\combase.dll
    Report Id: e6b49616-7de0-45a8-b7e6-659130f8c2dc
    Faulting package full name:
    Faulting package-relative application ID:

    Error 10/14/2019 11:32:23 AM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: combase.dll, version: 10.0.18362.356, time stamp: 0x3c1d04fa
    Exception code: 0xc0000409
    Fault offset: 0x0016a1fe
    Faulting process id: 0x481c
    Faulting application start time: 0x01d582a3d487b72b
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\WINDOWS\System32\combase.dll
    Report Id: e6b49616-7de0-45a8-b7e6-659130f8c2dc
    Faulting package full name:
    Faulting package-relative application ID:

    Error 10/14/2019 11:37:09 AM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Exception code: 0xc0000005
    Fault offset: 0x0003e3d6
    Faulting process id: 0x425c
    Faulting application start time: 0x01d582a4c7c4e2ec
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Report Id: 82aaf6af-64a6-4b11-a176-c77eecd4cd8d
    Faulting package full name:
    Faulting package-relative application ID:

    Error 10/16/2019 9:53:24 PM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Exception code: 0xc0000409
    Fault offset: 0x00444ac3
    Faulting process id: 0x32b4
    Faulting application start time: 0x01d58463b0beb906
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Report Id: 4abb1ea2-a23d-4c28-b4dc-57b463bdbaa3
    Faulting package full name:
    Faulting package-relative application ID:

    Error 10/17/2019 8:49:33 PM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Exception code: 0xc0000409
    Fault offset: 0x00444ac3
    Faulting process id: 0x452c
    Faulting application start time: 0x01d585207aa39946
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Report Id: c357de37-7d4f-4243-b842-d80f128acbed
    Faulting package full name:
    Faulting package-relative application ID:

    Error 10/21/2019 10:50:19 PM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Exception code: 0xc0000409
    Fault offset: 0x00444ac3
    Faulting process id: 0x7788
    Faulting application start time: 0x01d5885b14532622
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Report Id: c32ed489-1749-4d15-a5df-d9973d5c44a4
    Faulting package full name:
    Faulting package-relative application ID:

    Error 11/8/2019 11:00:09 AM Application Error 1000 (100)

    Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Faulting module name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5d30f77f
    Exception code: 0xc0000409
    Fault offset: 0x00444ac3
    Faulting process id: 0x251c
    Faulting application start time: 0x01d5963e1f55f15b
    Faulting application path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Faulting module path: C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe
    Report Id: c89f8cd0-def8-4797-8e3f-7c6d30e13bb6
    Faulting package full name:
    Faulting package-relative application ID:

  2. #2
    This is the first report I've seen of anything like this. I'm running the latest Windows 10 Home updated build without any issues. I leave FG running all the time.

    Does this happen just by opening a campaign, opening the image and waiting? Or are there more steps than that?
    I can try running the campaign that causes the issue on my machine to see if I can reproduce using the same steps.
    (Just zip up whole campaign folder, and post or PM. Make sure to reference this thread with the detailed steps.)

    Regards,
    JPG

  3. #3
    Thanks Moon Wizard. I have reloaded the campaign to the same state prior to the crash while I monitor memory usage. The only consistent step before the crash is FG at idle with the campaign open. The last crash must have happened before or during the process of saving the mask created just before I walked away because when I reopened the campaign, the mask was not on the image.

    Let me work on this a bit more before I send you the zip.

  4. #4
    After some evaluation the issue comes up on any campaign when an existing calendar log entry is left open. Here are the steps and observations from the evaluation. A campaign running with about 1.5 GB or more of FG usage made for the most obvious results.

    Create a log entry with a few paragraphs of text
    Close the log entry window
    Reopen the same log entry window
    Monitor Fantasy Grounds resource use in the Task Manager - Memory usage creeps up, cpu usages jumps, gpu usage starts.
    Close the log entry again
    Monitor FG resource - usage drops back to stable
    FG will close if/when the memory usage approaches the memory commit
    Issue is independent of campaign, calendar used, and occurs with no extensions using 5e ruleset. The Greyhawk, Realms and Gregorian were tested.
    The more memory a campaign is using, the more exaggerated the issue. Looked at new campaign only loading the calendar module around .5 GB, a 1 GB campaign, and 1.5 GB + campaign

  5. #5
    Trenloe's Avatar
    Join Date
    May 2011
    Location
    Colorado, USA
    Posts
    33,361
    Good find!
    Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!

  6. #6
    When you say "log entry", I'm not sure what you are referring to exactly. There are several things that could be called log entries.

    * Which ruleset is your campaign running?
    * What kind of "log entry" are you creating? (Please walk me through the steps of which buttons you push from starting campaign.)

    Thanks,
    JPG

  7. #7
    Trenloe's Avatar
    Join Date
    May 2011
    Location
    Colorado, USA
    Posts
    33,361
    Quote Originally Posted by Moon Wizard View Post
    When you say "log entry", I'm not sure what you are referring to exactly. There are several things that could be called log entries.

    * Which ruleset is your campaign running?
    * What kind of "log entry" are you creating? (Please walk me through the steps of which buttons you push from starting campaign.)

    Thanks,
    JPG
    @2bfjs mentions it's for 5E and it's a calendar log entry.
    Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!

  8. #8
    Trenloe's Avatar
    Join Date
    May 2011
    Location
    Colorado, USA
    Posts
    33,361
    Quote Originally Posted by 2bfjs View Post
    After some evaluation the issue comes up on any campaign when an existing calendar log entry is left open. Here are the steps and observations from the evaluation.

    Create a log entry with a few paragraphs of text
    Close the log entry window
    Reopen the same log entry window
    Monitor Fantasy Grounds resource use in the Task Manager - Memory usage creeps up, cpu usages jumps, gpu usage starts.
    I can recreate following these steps in a CoreRPG campaign using the Gregorian calendar.
    Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!

  9. #9
    Thanks for the info. I was eventually able to recreate. It happens if the player notes are scrolled off bottom of calendar log entry when opening, and it causes an endless redraw loop. There's a slow memory leak somewhere in the layout/redrawing code as well, but I wasn't able to identify that. However, I was able to identify the endless redraw loop issue, and I'll put the patch into the v3.3.9 version that should be releasing soon.

    Regards,
    JPG

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
5E Product Walkthrough Playlist

Log in

Log in