Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Important Important
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: None
    • Labels:

      Description

      You landed on this page because we have detected a crash in "X4 - Foundations".

      We are currently investigating the cause of the crash.

      This type of crash can actually be divided into two categories:

      1. caused by real low system memory conditions
      2. caused by an in-game issue

      Please follow the steps below in the given order to resolve the issue.

      Restricted virtual memory

      To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

      3rd-party mods

      A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigat it and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

      Further support

      If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to crash@egosoft.com with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see this page with details on how to locate the dump file on your drive).

      We'll update this issue here, once new details become available.

      Technical background

      The game uses Lua as one of its script engines. When a script is loaded or performs certain operations, memory is allocated. If this allocation fails a memory exception is raised, leading to this crash.
      We are aware this currently happens especially in two cases of the game:

      1. when the UI engine initializes (i.e. most likely when the user starts the game)
      2. at runtime while the game is running

      Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
      In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.

      Historical notes

      Before 3.30 Hotfix 1 Beta 1 the issue could occur in 'normal' situations. This was caused by the older Lua engine being limited to the lower 2GB of memory address space. Depending on 3rd-party tools, drivers, etc. users could run into this limit in common cases. 3.30 Hotfix 1 Beta 1 removed this limitation, so that the Lua engine can also use address space above the 2 GB range.

        Issue Links

          Activity

          Stefan Hett created issue -
          Stefan Hett made changes -
          Field Original Value New Value
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          If you are sure that the page file size setup is correct on your machine, we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-XXX - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-XXX - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Link This issue refers to X4-268 [ X4-268 ]
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-XXX - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Link This issue referred to by P1DEV-700 [ P1DEV-700 ]
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Comment [ Did you check the instructions pointed out at https://www.egosoft.com:8443/jira/browse/X4-268 ? ]
          Stefan Hett made changes -
          Comment [ As stated in the description above, we would be interested to get the details on the particular case triggering the crash. Without further details we unfortunately cannot look into the situation.

          With regards to your feedback on the build mode: I passed it on to the designer, but can't promise any update on the state of these. In general such feedback is better located in our forums here: https://forum.egosoft.com/viewforum.php?f=146 ]
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (located in the X4.exe folder).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          made changes -
          Attachment X4_r310_2020_05_03_15_11_23.dmp [ 28464 ]
          made changes -
          Attachment X4_r310_2020_05_05_09_45_13.dmp [ 28472 ]
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game addons, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Attachment X4_r310_2020_05_03_15_11_23.dmp [ 28464 ]
          Stefan Hett made changes -
          Attachment X4_r310_2020_05_05_09_45_13.dmp [ 28472 ]
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is risen, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate to some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          While we are working on a fix, you can try to mitigate the issue with the following steps:
          - try to start the game in a lower resolution (f.e. using 1920x1080 instead of running the game in 4k) - after the game started you can try if changing the game resolution in-game to the higher setting then still works
          - try to disable as many extensions as possible and see if this makes a difference
          - disable any other tool which might hook itself into the game (screen recorder software or tools which change/improve the graphics of the game are likely candidates)

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Link This issue refers to X4-454 [ X4-454 ]
          made changes -
          Attachment f4a8620b493e033e06f5c89dc136626c356a1f72.ico [ 28670 ]
          Attachment f4a8620b493e033e06f5c89dc136626c356a1f72.ico [ 28671 ]
          Stefan Hett made changes -
          Attachment f4a8620b493e033e06f5c89dc136626c356a1f72.ico [ 28670 ]
          Stefan Hett made changes -
          Attachment f4a8620b493e033e06f5c89dc136626c356a1f72.ico [ 28671 ]
          Stefan Hett made changes -
          Comment [ We are working on a fix for this particular situation which seems to trigger the problem for you. Once 3.30 is released we will provide instructions on this page for affected users and provide them with a specific fix for their systems. Please monitor this page for future updates and revisit it a day or two after 3.30 was released. ]
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          While we are working on a fix, you can try to mitigate the issue with the following steps:
          - try to start the game in a lower resolution (f.e. using 1920x1080 instead of running the game in 4k) - after the game started you can try if changing the game resolution in-game to the higher setting then still works
          - try to disable as many extensions as possible and see if this makes a difference
          - disable any other tool which might hook itself into the game (screen recorder software or tools which change/improve the graphics of the game are likely candidates)

          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 <= 3.30)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          A fix for this issue will be available with the next major game update (at the time of writing this, this is expected to be called version 4.00). In the meantime we provide a fix for the current version 3.30 for affected users.
          To get this fix, please follow the steps in the next section under *Further support*.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 <= 3.30)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          A fix for this issue will be available with the next major game update (at the time of writing this, this is expected to be called version 4.00). In the meantime we provide a fix for the current version 3.30 for affected users.
          To get this fix, please follow the steps in the next section under *Further support*.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 <= 3.30)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          A fix for this issue will be available with the next major game update (at the time of writing this, this is expected to be called version 4.00). In the meantime we provide a fix for the current version 3.30 for affected users.
          To get this fix, please follow the steps in the next section under *Further support*. We'll then send you instructions on how to apply the custom patch for 3.30, if we determined this is going to resolve your issue.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigated and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 <= 3.30)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          A fix for this issue will be available with the next major game update (at the time of writing this, this is expected to be called version 4.00). In the meantime we provide a fix for the current version 3.30 for affected users.
          To get this fix, please follow the steps in the next section under *Further support*. We'll then send you instructions on how to apply the custom patch for 3.30, if we determined this is going to resolve your issue.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigat it and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 <= 3.30)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          A fix for this issue will be available with the next major game update (at the time of writing this, this is expected to be called version 4.00). In the meantime we provide a fix for the current version 3.30 for affected users.
          To get this fix, please follow the steps in the next section under *Further support*. We'll then send you instructions on how to apply the custom patch for 3.30, if we determined this is going to resolve your issue.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigat it and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 <= 3.30)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash. Details about this particular problem are described in X4-454.
          A fix for this issue will be available with the next major game update (at the time of writing this, this is expected to be called version 4.00). In the meantime we provide a fix for the current version 3.30 for affected users.
          To get this fix, please follow the steps in the next section under *Further support*. We'll then send you instructions on how to apply the custom patch for 3.30, if we determined this is going to resolve your issue.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory can get allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigat it and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 < 3.30 Hotfix 1 Beta 1)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash.
          A fix for this issue is available in the current beta version. This [wiki entry|https://www.egosoft.com:8444/confluence/display/X4WIKI/Public+Beta+Tests] explains the details on how to opt in into the beta.Please give the beta a try and see if the start issue was resolved. If so, you can safely use this beta to continue playing. Once 3.30 Hotfix 1 was released, you can then opt out from the beta again.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory is allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          Stefan Hett made changes -
          Description You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigat it and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Game engine bug (X4 < 3.30 Hotfix 1 Beta 1)
          A third cause was identified. This issue applies to the Lua engine we are using and can trigger this crash.
          A fix for this issue is available in the current beta version. This [wiki entry|https://www.egosoft.com:8444/confluence/display/X4WIKI/Public+Beta+Tests] explains the details on how to opt in into the beta.Please give the beta a try and see if the start issue was resolved. If so, you can safely use this beta to continue playing. Once 3.30 Hotfix 1 was released, you can then opt out from the beta again.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory is allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.
          You landed on this page because we have detected a crash in "X4 - Foundations".

          We are currently investigating the cause of the crash.

          This type of crash can actually be divided into two categories:
          # caused by real low system memory conditions
          # caused by an in-game issue

          Please follow the steps below in the given order to resolve the issue.

          h3. Restricted virtual memory
          To rule out that you are suffering the crash because of a system setup issue, please refer to the instructions in X4-268 and verify that the virtual memory setup on your system is correct and doesn't artificially limit the available memory.

          h3. 3rd-party mods
          A second possible cause are 3rd-party game extensions/addons which allocate too much memory (usually this should be considered a bug in the addon/extension). If you are running the game with extensions/addons and are regularly running into this crash, try to trace down the problematic addon by disabling one addon after another. If you could determine the problematic addon, just leave a comment in this issue and we'll investigat it and if we can confirm the issue, add the addon to the known list of addons which can cause this crash.

          h3. Further support
          If you are sure that the page file size setup is correct on your machine and no 3rd-party addon seems to trigger the crash (or if you are running the vanilla client), we'd like to get information about what might have triggered the crash. If you are aware of a way to reproduce the issue, please send a mail to [mailto:crash@egosoft.com] with the subject set to "X4-281 - In-game crash - 475669", describe how to trigger the crash (if the repro case requires loading a savegame, please make the savegame available - f.e. by uploading the save to OneDrive or GoogleDrive and send us the link), add a list of enabled game extensions, attach a screenshot of the machine's page file setup as described in X4-268, and the dump file (see [this page|https://www.egosoft.com:8444/confluence/display/X4WIKI/Crash+Reports+and+Crash+Dumps#CrashReportsandCrashDumps-Locatinglocalcrashreports] with details on how to locate the dump file on your drive).

          We'll update this issue here, once new details become available.

          h1. Technical background
          The game uses [Lua|https://www.lua.org/] as one of its script engines. When a script is loaded or performs certain operations, memory is allocated. If this allocation fails a memory exception is raised, leading to this crash.
          We are aware this currently happens especially in two cases of the game:
          # when the UI engine initializes (i.e. most likely when the user starts the game)
          # at runtime while the game is running

          Usually the memory consumption of Lua is quite low and a crash when starting the game should indicate some arbitrary machine restrictions (i.e. limited available memory way below what the min-specs require). A crash at runtime however can also be triggered by requesting a ridiculous amount of memory.
          In vanilla games, this should never happen and if it does, is considered a bug which we will fix ASAP.

          h3. Historical notes
          Before 3.30 Hotfix 1 Beta 1 the issue could occur in 'normal' situations. This was caused by the older Lua engine being limited to the lower 2GB of memory address space. Depending on 3rd-party tools, drivers, etc. users could run into this limit in common cases. 3.30 Hotfix 1 Beta 1 removed this limitation, so that the Lua engine can also use address space above the 2 GB range.

            People

            • Assignee:
              Stefan Hett
              Reporter:
              Stefan Hett
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: