Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 02-28-2021, 10:45 PM   #1
mgrtoma
Human being with feelings
 
Join Date: Aug 2020
Posts: 16
Default Crash during scan of the library database (FIXED)

Hello,

I have an issue with the v6.23 feb4 2021 of Reaper (Mac). During the scan of my Sound Library on my internal HDD, while doing nothing else, Reaper suddenly closes and crash, back to the desktop. I'm using Mac OS Mojave with the latest updates, 32Gb ram, i7 CPU.
I didn't have this problem last summer when scanning the same HDD and Sound Library.
In order to solve the problem I did a full checkup on my HDD, Repair + DiskWarrior, but it didn't fix the issue in Reaper, the HDD is fine.

I attached the Debug info if it can help.


I will take any advice to make it work, Thank you.
Attached Files
File Type: txt Reaper Database scan bug.txt (101.8 KB, 232 views)

Last edited by mgrtoma; 02-28-2021 at 10:54 PM.
mgrtoma is offline   Reply With Quote
Old 03-03-2021, 03:59 AM   #2
mgrtoma
Human being with feelings
 
Join Date: Aug 2020
Posts: 16
Default

FIXED with REAPER v6.24 Final. Thank you !
mgrtoma is offline   Reply With Quote
Old 03-07-2021, 03:05 AM   #3
mabian
Moderator
 
mabian's Avatar
 
Join Date: Aug 2007
Location: Italy
Posts: 4,327
Default

A friend of mine experienced some crashes while browsing many Cymatics free sound banks with media explorer (not database scan, just browsing them) on Windows.

It seems it's solved on 6.25.

In this thread the issue on Mac is reportedly fixed on 6.24, while there's a 6.25 log entry referring to the very same thread:

"WAV: fix potential crash when reading .wav files written by other applications [t=250134]"

So, could it be the same problem? And was it fixed in 6.24 or 6.25?

Thanks,
Mario
mabian is offline   Reply With Quote
Old 03-07-2021, 05:40 AM   #4
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,741
Default

The likely case is that the bug described in this thread was not fixed in 6.24, but in 6.25. This bug occurred if some .wav media had iXML with broadcast wave time, encoded with only a low 32-bits and no 32-bits, and would occur when reading metadata from the media explorer, or moving that item to source preferred position, or opening the source properties
Justin is online now   Reply With Quote
Old 03-07-2021, 02:13 PM   #5
mabian
Moderator
 
mabian's Avatar
 
Join Date: Aug 2007
Location: Italy
Posts: 4,327
Default

Thank you so much for the detailed explanation, Justin.

- Mario
mabian is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 04:50 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.