You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@echo off
rem the `mem` command is removable since it's only for debugging
mem
rem recursively calls command.com
%comspec% /c %0
the DOSBox-X crashed even before exhausting the whole memory:
When I changed the line to %comspec% /c %comspec% /c %0, the bug appeared as usual, but the amount of memory is slightly different:
Steps to reproduce the behaviour
1.Download any latest DOSBox-X versions (as this bug appears on nearly all specific versions, even on older DOSBox 0.74 or DOSBox SVN) .
Create a batch file and save it as recurse.bat in the same directory as dosbox-x.exe:
@echo off
rem the `mem` command is removable since it's only for debugging
mem
%comspec% /c %0
It's advisable not to directly open it since it can directly be run on Windows.
2.Run it via dragging the recurse.bat to dosbox-x.exe in Windows Explorer, or open dosbox-x.exe and input:
mount c .
c:
recurse
Then you will see Werfault.exe unexpectedly appear in Windows Task Manager.
Expected behavior
The batch file runs normally until all the conventional memory is exhausted.
When the memory is exhausted, DOSBox should display a message like "Program too big to fit in memory" similar to the behavior of MS-DOS.
What operating system(s) this bug have occurred on?
Windows 10 22H2 (note: the screenshot shows my win7 theme, but it is actually on win10)
Describe the bug
When executing:
the DOSBox-X crashed even before exhausting the whole memory:
When I changed the line to
%comspec% /c %comspec% /c %0
, the bug appeared as usual, but the amount of memory is slightly different:Steps to reproduce the behaviour
1.Download any latest DOSBox-X versions (as this bug appears on nearly all specific versions, even on older DOSBox 0.74 or DOSBox SVN) .
Create a batch file and save it as
recurse.bat
in the same directory asdosbox-x.exe
:It's advisable not to directly open it since it can directly be run on Windows.
2.Run it via dragging the
recurse.bat
todosbox-x.exe
in Windows Explorer, or opendosbox-x.exe
and input:Then you will see
Werfault.exe
unexpectedly appear in Windows Task Manager.Expected behavior
The batch file runs normally until all the conventional memory is exhausted.
When the memory is exhausted, DOSBox should display a message like "Program too big to fit in memory" similar to the behavior of MS-DOS.
What operating system(s) this bug have occurred on?
Windows 10 22H2 (note: the screenshot shows my win7 theme, but it is actually on win10)
What version(s) of DOSBox-X have this bug?
2025.01.01 SDL2 MinGW, commit 895fca3
Used configuration
Output log
Additional information
The debugger window not outputting any message:
The output when executing the same file in DOSBox-SVN debugger that might offer some help:
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines
The text was updated successfully, but these errors were encountered: