PDA

View Full Version : Changing artist to Collaboration crashes OrangeCD


tearaway
12-19-2013, 01:37 AM
OrangeCD Suite version 6.5.0 and build number 18002.
Win8 operating system version, English

When editing some fields on entries, such as changing to a Collaboration for artist on a CD entry, the application reliably crashes. This also happened on a Win7 64bit system, same DB. OrangeCD's crash log fails to send when bringing the application back up (attached image). The crash image is attached. From Event Viewer, this is the description of the crash. I do not have Norton anything installed, although I do use Avast A/V. Any advice is appreciated!


Log Name: Application
Source: Application Error
Date: 12/18/2013 8:11:04 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: GatewayLaptop
Description:
Faulting application name: dadbapp.exe, version: 6.5.0.18002, time stamp: 0x50bc018d
Faulting module name: ntdll.dll, version: 6.2.9200.16578, time stamp: 0x515fac6e
Exception code: 0xc000041d
Fault offset: 0x000616ad
Faulting process id: 0x938
Faulting application start time: 0x01cefc5716fd934f
Faulting application path: C:\Program Files (x86)\OrangeCD\dadbapp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 6ddc1ef8-684a-11e3-be78-206a8abc0af4
Faulting package full name:
Faulting package-relative application ID:
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="2013-12-19T01:11:04.000000000Z" />
<EventRecordID>1730</EventRecordID>
<Channel>Application</Channel>
<Computer>GatewayLaptop</Computer>
<Security />
</System>
<EventData>
<Data>dadbapp.exe</Data>
<Data>6.5.0.18002</Data>
<Data>50bc018d</Data>
<Data>ntdll.dll</Data>
<Data>6.2.9200.16578</Data>
<Data>515fac6e</Data>
<Data>c000041d</Data>
<Data>000616ad</Data>
<Data>938</Data>
<Data>01cefc5716fd934f</Data>
<Data>C:\Program Files (x86)\OrangeCD\dadbapp.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>6ddc1ef8-684a-11e3-be78-206a8abc0af4</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

**************************************
"Don't be normal, be natural!"
http://www.facebook.com/outsight
http://twitter.com/outsightradio
http://www.goodreads.com/tearaway
http://outsight.podomatic.com/
Search for "Outsight Radio Hours" in iTunes!


50
andrei_c
12-19-2013, 11:00 PM
Hey tearaway - I just sent you an email. Thanks

Andrei
gurnemanz
12-20-2013, 05:18 PM
Whilst on collaboration, this useful feature is still a bit buggy in some respects.

1) the error mentioned by me here over a year ago
http://www.firetongue.com/boards/showthread.php?8576-collaboration-error

2) I have noticed that sometimes for no obvious reason artists properly entered as a collaboration later appear decollaborated (if that word exists) eg Tom & Jerry as one unit. I then have to go back and separate them again.
Joebugs
12-20-2013, 07:59 PM
Yes, happens to me too. It happens when you update album data, main suspect is when you update track artist.
tearaway
01-22-2014, 01:44 AM
Thank you for the responses. Andrei - I never seen a response to my email for sending you a copy of my DB. Did you receive it? Does it seem corrupted?

While the application crashes routinely on setting up collaborations, it also happens sporadically on other fields, like setting the date of the recording. This happens on different PCs using copies of the same OrangeCD.

I have 100s of hours of work entering data on nearly 20K releases, so I am concerned about my ability to move forward with OrangeCD

Is it possible to export the data all the way to track level in some format more portable than OrangeCD's proprietary XML format?
tearaway
02-12-2014, 05:59 PM
This is really frustrating. I try to have OrangeCD send its crash report, but I always get back "Bad HTTP Status Code" Did the review of the copy I sent in December yield anything? I upgraded to 6.5.1, but still have the regular crashes routinely when trying to set up an album-level collaboration, occasionally editing other fields. I feel it has something to do with the size of my DB, or some content ...
andrei_c
02-19-2014, 10:27 PM
I believe the issue with collaboration editor is finally fixed in today's build. It was an elusive bug.

On to "Bad HTTP Status code", can you post session log for this? You can grab it from the same window where the error is, on a separate tab.

Andrei
tearaway
02-20-2014, 02:00 AM
Andrei -

Thanks! I had album that routinely crashed every time I tried to change to a collaboration, and it works in this build! I will push the application more in the coming days if an issue arises.

As for the session log, it is empty as you can see:


51
gurnemanz
02-21-2014, 11:34 AM
I believe the issue with collaboration editor is finally fixed in today's build. It was an elusive bug.

On to "Bad HTTP Status code", can you post session log for this? You can grab it from the same window where the error is, on a separate tab.

Andrei

But this ongoing collaboration error is still there:

http://www.firetongue.com/boards/showthread.php?8576-collaboration-error
Jazz_North
02-21-2014, 01:56 PM
As is this one:

http://www.firetongue.com/boards/showthread.php?9030-Collaboration-and-Artist-Sort-Name


But this ongoing collaboration error is still there:

http://www.firetongue.com/boards/showthread.php?8576-collaboration-error
gurnemanz
02-28-2014, 10:02 AM
But this ongoing collaboration error is still there:

http://www.firetongue.com/boards/showthread.php?8576-collaboration-error

Latest update has corrected this! Thanks very much, Andrei.
tearaway
03-09-2014, 06:47 PM
Just to let you know, I have entered scores of CDs including many with collaborations and had no issues on the newest build - thanks much for fixing this.
gurnemanz
04-08-2014, 10:15 PM
Whilst on collaboration, this useful feature is still a bit buggy in some respects.


I have noticed that sometimes for no obvious reason artists properly entered as a collaboration later appear decollaborated (if that word exists) eg Tom & Jerry as one unit. I then have to go back and separate them again.

Quoting myself here. The above error is still happening. It is annoying and fiddly to have to go back and re-enter these collaborations that have joined togther.
Jazz_North
04-09-2014, 01:18 PM
And many of the collaborations - as I have pointed out a number of times - still do not get the proper sort names. The proposed solution actually made things worse.