Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: 0.7.7a memory leak? (Read 2107 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

0.7.7a memory leak?

This has happened to me two nights in a row now.  I was listening to this "128k MP3 Proxy" stream and I would guess getting close to one hour, my computer locks up solid.  XP, 512 ram, etc.

Run this stream for a while and see if it locks up your machine:

http://somafm.com/gs8000.pls

0.7.7a memory leak?

Reply #1 –
I ran it for about 40 minutes and did see a memory increase after it had settled down.  During that time memory usage went up by about 3 meg and was still growing.  Seems to grow only when the songs change, but I could be mistaken.  My system did not crash during that time. Since I have tons of spare system resources I'm probably not a good test machine, however

fb2k 7.7a

P4 3.0 ghz
1 gig RAM
XP w/SP1
120 gig free disk
Paging file 1.5 gig. - 256 meg in use
Master of Fate. By Fate Mastered

0.7.7a memory leak?

Reply #2 –
Quote
I ran it for about 40 minutes and did see a memory increase after it had settled down.  During that time memory usage went up by about 3 meg and was still growing.  Seems to grow only when the songs change, but I could be mistaken.  My system did not crash during that time. Since I have tons of spare system resources I'm probably not a good test machine, however

fb2k 7.7a

P4 3.0 ghz
1 gig RAM
XP w/SP1
120 gig free disk
Paging file 1.5 gig. - 256 meg in use

"Mem usage" or "VM size" in task manager ? If it's the former, it your "memory leak" will magically go away as soon as you minimize fb2k.
Other than that, system freezes come from broken drivers/hardware, not from app memory leaks, so it's classified as a false bug report already.
Microsoft Windows: We can't script here, this is bat country.