The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 66 - File: global.php(961) : eval()'d code PHP 8.0.28 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/global.php(961) : eval()'d code 66 errorHandler->error_callback
/global.php 961 eval
/showthread.php 28 require_once
Warning [2] Undefined property: MyLanguage::$thread_modes - Line: 43 - File: showthread.php(1617) : eval()'d code PHP 8.0.28 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php(1617) : eval()'d code 43 errorHandler->error_callback
/showthread.php 1617 eval




False Alarm 0.9c - Dwelvers Dump File Size
#1
When Dwelvers crashes (for whatever reason), it can fill up your computer with 0.5GB of dump data. Data which is often not used for error analysis.

This is not a crash, but more of an awareness issue.

   

I've got two files of crash data that basically uses 1GB. Use Revo-uninstaller to see how much you have.

http://www.revouninstaller.com/revo_unin...nload.html

This is not advertising, I would say it is concern for my fellow Dwelvers.
Reply
#2
That's interesting. I don't even have a CrashDump folder. Pretty sure I haven't used CCleaner in a while, and Dwelvers crashed on me at least once in the 0.9-0.9b test phase. Have you modified your registry settings for Windows Error Reporting?
Reply
#3
This seems to be some kind of option you have activated in windows, the 0.5gb dump size seems to be matching the amount of memory Dwelvers uses, and I do know that when a crash occurs the user can get an option to dump the memory to a file, but this is nothing I can control, it is a windows settings only.
You can google "Disable Windows application crash dumps" to get some more information about this.

Marked as false alarm.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)