#16 GUI Crash when Saving Bext and MD5 Sum; WaveLab 7.2.1 Bext

open
nobody
None
9
2013-05-20
2012-10-11
charetted
No

Hello,

I've been having some issues with the BWF MetaEdit GUI v1.2.0 crashing repeatedly when saving MD5 check-sums and updating the Bext version from 1 to 2. I've been testing wave files from various applications, and it seems that files created in WaveLab versions 6 and 7.2.1 are causing BWF MetaEdit to crash more often than files from other applications (Pro Tools, Audacity, general wave test files from the web), if they include any INFOlist metadata created by WaveLab. If I do not embed metadata from WaveLab prior to using BWF MetaEdit, the application seems to handle the files just fine. I've tried running the application as admin, and in various windows compatibility modes. I've installed the 32 and 64 bit versions on Windows 7 and Windows XP workstations, and notice the same symptoms across platforms.

I can repeatedly recreate the problem on two machines in our office using the steps below:

1. Embedding an MD5 check-sum
Steps to recreate the problem: Open BWF Metaedit, Set option to generate and embed MD5 check-sum, Import Wav Files, Save - application crashes, but seems to write 1 check-sum each time.

2. Changing the Bext version from 1 to 2, then saving
Steps to recreate the problem: Open BWF Metaedit, Import Wave Files, Toggle Bext version from 1 to 2, Save - application crashes, but seems to write 1 Bext version change each time.

Once the check-sum and Bext version have been successfully saved, the application functions normally with no additional issues.

My computer specifications are as follows:
OS: Windows 7 Pro SP1
CPU: Intel Core i7-2600 CPU @ 3.40GHz
RAM: 16GB
System Type: 64-bit

The second test machine specifications are:
OS: Windows XP SP3
CPU: Intel Core 2 DUO E7500 @ 2.92 GHz
RAM: 2GB
System Type: 64-bit

Here is a recent error log that I was able to pull from MS Event Viewer:
Event 1000 - Application Error:

Faulting application name: bwfedit-gui.exe, version: 1.2.0.0, time stamp: 0x4f478c71
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000005
Fault offset: 0x000000000004e4b4
Faulting process id: 0x1114
Faulting application start time: 0x01cda7befdc0a305
Faulting application path: C:\Program Files\FADGI\BWF MetaEdit\bwfedit-gui.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5799b425-13b2-11e2-93e3-3860779cb09b

Log Name: Application
Source: Application Error
Date: 10/11/2012 10:51:23 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: *Removed for security
Description:
Faulting application name: bwfedit-gui.exe, version: 1.2.0.0, time stamp: 0x4f478c71
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000005
Fault offset: 0x000000000004e4b4
Faulting process id: 0x1158
Faulting application start time: 0x01cda7bfd4007465
Faulting application path: C:\Program Files\FADGI\BWF MetaEdit\bwfedit-gui.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 1fdfeac5-13b3-11e2-93e3-3860779cb09b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-11T14:51:23.000000000Z" />
<EventRecordID>6333</EventRecordID>
<Channel>Application</Channel>
<Computer>*Removed for security</Computer>
<Security />
</System>
<EventData>
<Data>bwfedit-gui.exe</Data>
<Data>1.2.0.0</Data>
<Data>4f478c71</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec4aa8e</Data>
<Data>c0000005</Data>
<Data>000000000004e4b4</Data>
<Data>1158</Data>
<Data>01cda7bfd4007465</Data>
<Data>C:\Program Files\FADGI\BWF MetaEdit\bwfedit-gui.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>1fdfeac5-13b3-11e2-93e3-3860779cb09b</Data>
</EventData>
</Event>
------------------End Error Log-----------------------------

I've also attached a screenshot of an error message that sometimes pops up after BWF MetaEdit crashes. Perhaps you will find it useful.

Thank you for looking into this!

Discussion

  • charetted

    charetted - 2012-10-11

    Memory Ref. Error Message

     
  • charetted

    charetted - 2012-10-11

    It turns out the Bext data from WaveLab is to blame, and not the INFOlist as I previous thought. BWF MetaEdit does not crash when INFOlist data is added, but does when Bext data created in WaveLab exists prior to editing with MetaEdit.

     
  • charetted

    charetted - 2012-10-15
    • summary: GUI Crash when Saving Bext and MD5 Sum; WaveLab 7.2.1 INFO --> GUI Crash when Saving Bext and MD5 Sum; WaveLab 7.2.1 Bext
     
  • AudioVisualPreservationSolutions

    • priority: 5 --> 9
     
  • AudioVisualPreservationSolutions

    This is Fixed - WaveLab files no longer crash program

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks