Menu

#62 RedVex/AO Memory leak causes crashes + Drwatson report

RC1-RC25
closed
kingsob
5
2008-07-12
2008-06-15
ToDo Waldi
No

Hello.
I noticed, that at a fresh start of RedVex+D2Loader, both exes do not consume much Memory (look in Task Manager).
But if you sit there with your Task Manager you can see, that both programs increase their Memory usage constantly, second for second.
Until RedVex crashes!

When a process crashes, the program drwtsn32.exe of Windows creates a log about the crashs.
I uploaded my log here:
http://home.arcor.de/ToDoWaldi/Spiele/Diablo%20II/drwtsn32.rar

I have no clue what the pieces of information mean, but i found out the following things:
1. I get two types of exception errors:
a. Exception number: 80000007
b. Exception number: c0000005 (access violation)
I get these again and again.

and that:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for C:\D2\Awesom-O\todowaldi.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\kernel32.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\WS2_32.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\D2\Awesom-O\Plugins\Awesom-O.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\D2\Awesom-O\pthreadVC2.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\msvcrt.dll
and various other dll files listed

everytime something about "symbol"

hope that can help you to stop redvex from crashing!

Discussion

  • ToDo Waldi

    ToDo Waldi - 2008-06-15
    • assigned_to: nobody --> kingsob
     
  • Kelani Z

    Kelani Z - 2008-06-15
    • labels: 1108230 --> Mechanics/Timing
    • milestone: 846288 --> RC1-RC25
    • summary: Things that might help to stop RedVex from crashing... --> RedVex/AO Memory leak causes crashes + Drwatson report
     
  • Kelani Z

    Kelani Z - 2008-06-15

    Logged In: YES
    user_id=193557
    Originator: NO

    Are you using version 3.5.6 or a recent beta? Many of the leaks have been fixed in betas released in the last 2 weeks.

    Please let us know what version you're using. Otherwise, we will assume you're using 3.5.6 where this problem is known to exist. If no info is posted in a few days, this bug report will be set to Pending, and if it still isn't updated within 14 days after that, it will be deleted.

     
  • Kelani Z

    Kelani Z - 2008-06-27

    Logged In: YES
    user_id=193557
    Originator: NO

    This bug report has been marked Pending, as we need more information from you to be able to help. Your report will remain in Pending status for 14 days at which point it will be deleted unless you update it by adding a comment with more detailed info explaining the problem.

    Please update your report within 14 days! If you don't, it is automatically deleted and cannot be reopened. Once this happens, you will have to submit a new report if you want us to look at this issue.

    When updating your bug report, some things we need to know are:

    1.What Redvex and Awesom-O versions you're using
    2.Exactly what you were doing when it happened
    3.Exactly where it happened
    4.Your OS,CPU speed and Internet provider and connection type.
    5.The character class you were using when it happened.

    Please also include your bot.ini, Awesom-O.ini and Awesom-O.log files if applicable, as these might help us diagnose the problem.

    Be sure to remove all personal info from your ini such as account names/passwords and cd keys first!

    If your bug report is not updated within the next 14 days, it will be permanently closed and you will have to submit a new report.

    Thanks!

    AO DevTeam

     
  • Kelani Z

    Kelani Z - 2008-06-27
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

MongoDB Logo MongoDB