|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #49927] wavread/audioread refuses to continue reading wav-file |
Date: | Mon, 26 Dec 2016 15:19:47 +0000 (UTC) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #3, bug #49927 (project octave): This bug is reported against version 4.0.0 which is deprecated. Could the original reporter try again with the recent stable release of Octave (4.2.0)? A lot has improved since 4.0.0, and you can try the 32-bit or 64-bit version of Octave-4.2.0 as Philip suggests. If neither the 32-bit or 64-bit version solve the problem then there might be an issue worth debugging here. The size of the data read is not all that large: size = 4000*4096*4 = 65 MiB If there are clues in the file about the eventual size of the output then Octave could do one single allocation at the start of the read, rather than re-sizing an array each time through the loop. This would help prevent memory fragmentation in the heap. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?49927> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |