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
Before reporting a crash, please make sure you've gone through the following steps first:
Check to see whether the crash is still present in the latest dev version.
Once you've confirmed the crash is still present, go through the steps necessary to trigger the crash. Once the application has crashed, it may show a dialog indicating that a crash dump has been created. If that's the case, attach the crash dump here. The dump file should be created in %TEMP% and be named something like Explorer++1.4.0.0-11102020-194414.dmp.
If no crash dump is generated, run the latest dev version with the --enable-logging command line flag. A few logging files should be created in %TEMP%. If a file named something like Explorer++.exe.DESKTOP-1234.User.log.FATAL.20240405-190058 contains any logging lines, attach that file here. Depending on how the crash occurs, it's possible that the log file may contain useful information, even if no crash dump is generated.
If no crash dump is generated and the log files contain no relevant information, please describe the crash in detail.
Describe the crash
Not really clear based on the instructions if I'm even supposed to still submit this, since the crash doesn't happen with the dev build, but every time I access certain drives (mostly mirrors of each other, so the content is mostly the same), it crashes. It seems to happen when it starts gathering details for a very large directory, presumably the size is tripping it up, though no idea why it's not happening with the dev build (it also rescans the directory sizes every time, which is very slow, and seems it would be better to only do so after changes). Disabling the option to show folder sizes fixes it, so that seems to confirm that's the issue. The dev build has that option checked, but it's not showing the sizes, so that's likely why it's not crashingvery slow, though it eventually loads them and doesn't crash, even when loading the sizes of directories significantly larger than the one that seems to be crashing the regular version.
To Reproduce
Steps to reproduce the crash:
Access directory (with very large subdirectory?)
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):
Explorer++ version: 1.4.0.2293 (64-bit build)
OS: Windows 10
Additional context
It would make it a lot easier and probably help users and therefore make it more likely for them to submit crash reports if the dev build were included here, instead of having to go find it on the main website.
The text was updated successfully, but these errors were encountered:
Before reporting a crash, please make sure you've gone through the following steps first:
Describe the crash
Not really clear based on the instructions if I'm even supposed to still submit this, since the crash doesn't happen with the dev build, but every time I access certain drives (mostly mirrors of each other, so the content is mostly the same), it crashes. It seems to happen when it starts gathering details for a very large directory, presumably the size is tripping it up, though no idea why it's not happening with the dev build (it also rescans the directory sizes every time, which is very slow, and seems it would be better to only do so after changes). Disabling the option to show folder sizes fixes it, so that seems to confirm that's the issue. The dev build has that option checked, but it's
not showing the sizes, so that's likely why it's not crashingvery slow, though it eventually loads them and doesn't crash, even when loading the sizes of directories significantly larger than the one that seems to be crashing the regular version.To Reproduce
Steps to reproduce the crash:
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):
Additional context
It would make it a lot easier and probably help users and therefore make it more likely for them to submit crash reports if the dev build were included here, instead of having to go find it on the main website.
The text was updated successfully, but these errors were encountered: