Memory Leak & File Association problems
Status: Beta
Brought to you by:
d0c54v4g3
In the last few days, my Rufus suddenly got the habbit
of taking endless and evergrowing amount of memory. I'm
talking about over 700 MB of Working Set and over 1,400
MB of Virtual Set here, before the system is so slowed
down I have to terminate Rufus hardcore.
Unfortunately I don't have a good idea how this
happened exactly. It begann when Rufus failed to open a
few torrents with obviously illegal format (created by
the infamous evil BitComet), but even after I removed
those torrents (both in the queue and on hard disk) the
problem reaccurred. So I'm at lost about this, I still
feel obliged to report the bug since it's a big deal
when a program claims over a GB of memory.
Logged In: YES
user_id=1112940
It's good that you posted this. I'm sure there are many
more bugs that I never hear about.
Here is a list of questions that might aid in tracking down
this bug.... Do you still have a copy of the torrents you
were using? Can you tell me how Rufus was started? -
Running the exe directly, double clicking on a torrent,
loading a torrent from a browser. How many torrents were
loaded when the error occurred? What other applications had
you been running? Can you attach a copy of your
btconfig.ini? (Remove your webui password if you have one)
The above info might give me something to go on...
Thanks
d0c
Logged In: YES
user_id=622839
> Do you still have a copy of the torrents you were using?
I might have.
> Can you tell me how Rufus was started?
Rufus was started manually (file association does not work,
btw, since the "Associate Rufus with .torrent files" button
has no effect, but that's obviously a different bug) and the
"illegal" torrents were loaded manually via URL (within
Rufus) first, and manually as local files later (after my
first killing of the program).
> How many torrents were loaded when the error occurred?
Two which were paused, two or three "illegal" ones that
didn't start, two or three having problems connecting to
their unreliable tracker from time to time, and two or three
running normally.
> What other applications had you been running?
Nothing suspisous. As a system admin of a computer lab I'm
pretty sure there was no obvious interference from other
applications. Specially, there was no anti-virus or firewall
software running (yes, I trust myself enough not to get
infected despite lack of anti-virus software, and our
external firewall is reliable enough).
> Can you attach a copy of your btconfig.ini?
Later I might.
Logged In: YES
user_id=1112940
Hey,
RE Associate button:
Can you post the contents of this registry key here:
HKEY_CLASSES_ROOT\bittorrent\shell\open\command
This might indicate why the association is broken as this is
the key that Rufus resets when the "Associate Rufus with
.torrent files" button is pressed.
Have you had any luck replicating the leak? I'll see if I
can get Rufus to max out my memory here, but if I can get
the .torrent files and the btconfig.ini from you that would
be useful. You can mail them to me via the e-mail address
on the rufus homepage as it's probably safer than posting
them here.
Thanks for the help
d0c
Logged In: YES
user_id=622839
Regarding the file association problem: the registry key you
mentioned was set to: "X:\Tools\Rufus\rufus.exe""%1" (4
quotation marks total), it looked somewhat odd to me and I
added a space between the two consecutive quotation marks.
In either case .torrent files would still fire up Azureus
when double clicked (or otherwise triggered by the OS). So
obviously this registry key Rufus sets is overruled by some
other settings.
As for the question if I can reproduce the memory leak, I'd
guess I could, though I don't really want to try, since the
leak takes hours and even up to days until it becomes
significant (at which time I might be away and cannot take
measures to terminate the near-deadlock).
The troubling .torrent file is being sent to
<c4n15.rufu5@gmail.com> (not sure if this is the mail
address you referred to), along with my .ini file. Please
note Azureus also behave strangely with that .torrent and
cannot download the files.