- This topic has 4 replies, 2 voices, and was last updated 14 years, 7 months ago by
.
-
Posts
-
I was joking:
"I have found an unbelievable bug."And now I have to write it again.
But this time it is not a joke.My problem with build 94:
It eats endless memory.
After running it for approx. one hour, I got a message that Windows (XP pro SP2)
was running out of memory on my system partition.
The "luck" was that I had only 800 MB free space on it.
"Luck" because if you have some gigabytes free on your system partition, you won’t notice it.With Disc Cleanup I could free it by deleting "Temporary files".
I restarted Breakaway Live build 94 and kept an eye on the free memory on my system partition.
It eats approx. 10 MB per minute.
Restarting Breakaway (or change the I/O configuration settings) frees the memory, but the memory eating starts again.Using build 93 (installation on top of build 94) this memory problems does not occur.
Build 94 is writing a "dump.wav" file located in the Breakaway Live program folder.
Is this a special hidden bug tracking function for analysis purpose ?
Do you (Leif) have forgotten to disable it for the public beta release ?
Is there a way to disable this dump.wav writing (I cannot delete it while Breakaway is running – access denied) by editing the INI file ?
I had a quick look on the INI, but I could not find a relating key.Or do we have to wait for new build to fix this ?
Personally I can free some extra disk space (a few gigabytes) and delete the dump.wav after every shutdown of Breakaway Live.
I hope you can reproduce this "problem" Leif.
I have found a dirty workaround trick to disable the dump.wav writing:
1. After the shutdown of Breakaway Live 0.90.94 I deleted the dump.wav.
2. I created a new (empty) .txt file with Notepad inside the Breakaway program folder and renamed it to dump.wav.
3. I opened the file properties and enabled the "Read-only" option (attributes).
-> Breakaway Live 0.90.94 cannot access the file ❗ 😉
Oops!
[quote author=”michi95″]Is this a special hidden bug tracking function for analysis purpose ?Do you (Leif) have forgotten to disable it for the public beta release ?[/quote]
Yes. I use wave dumping the way an electronics engineer would use oscilloscope probes.
In Breakaway Live, I enabled wave dumping to test the latency of the processing. Channel 1 of the output file is Left channel before processing, Channel 2 is left channel after processing. Thus, by playing clicks into the breakaway input, and looking at the output in Adobe Audition, I could get an exact figure of how much latency the processing is adding.
I forgot to take it out for the release. My bad! Will take it out for 0.90.95. Thanks for finding it 🙂.
///Leif
It is very good that you already have compiled build 95 .
Thank you very much !Approx. ten times my dirty workaround (creating one time my own write protected dump.wav file inside the Breakaway Live program folder) solved this problem with build 94.
Though I thought that it worked this way, I checked the system partition free memory and the contents of the Breakaway Live program folder from time to time while build 94 was running.
And one time it started again.
I was loosing 10 MB per minute.
I looked inside the Breakaway Live program folder.
Everything seems alright, because my dummy dump.wav had still 0 bytes. 😯
➡ 💡 Using the Windows search I found another dump.wav file inside
C:Documents and SettingsMichi
(the user account I am using)
It already had 436 MB (running BA Live for 43 minutes).
But this one I could delete.It does not happen again.
I cannot reproduce it.
Any idea why BA Live build 94 wrote the dump.wav to
C:Documents and SettingsMichi ❓So it is good to have the update build 95 !
Hi Michi!
[quote author=”michi95″]Any idea why BA Live build 94 wrote the dump.wav to C:Documents and SettingsMichi [/quote]
Yes, actually.
To write INI files etc, I check what folder Breakaway is running from, and make sure the file ends up in that directory.
On the other hand, "dump.wav" is just written to the current directory. So, if you for example have a shortcut to Breakaway Live with the "Start in:" blank, the current directory will be your user folder.
So, you must have (for example) started it with a shortcut once, and started it by clicking on the EXE once, or something like that. 🙂
Best,
///Leif
- The forum ‘Breakaway Professional Products – [discontinued]’ is closed to new topics and replies.