MP3-Boss forum

Questions, comments and concerns about MP3-Boss: MP3 Database and Manager

You are not logged in.

Announcement

MP3-Boss Facebook Group
v0.683 is the official release. * Beta info * Have you checked the MP3-Boss Facebook Page? My contact address is MP3-Boss primary email address.
Returning users: Send me an email containing your user name, and I'll reset your email address (old info was lost during a crash).

#1 2007-03-22 09:44:41

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Lockup when scanning in v0.616?

I just got a "v0.616 will lockup during scanning" report -- not quite enough details for me to figure out what is going on (although I hope I'll get some more information).

The report was for 2 different WinXP computers.   Instead of an MP3-Boss error, it looks like it was an Access crash message.  I DID fix such a problem in v0.614 when scanning very long paths (status bar is limited to 255 chars).

Has anyone else been seeing this?  I've been scanning a LOT as I prepare for v0.617 (which will support a lot of new file formats), and haven't seen the problem.

Offline

 

#2 2007-03-25 15:57:54

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Re: Lockup when scanning in v0.616?

Also...the strangest thing about the report is that it is an Access error -- not the normal "MP3-Boss" error message.

"Microsoft Access has encountered a problem and needs to closed. We are sorry for the inconvienence."

Anybody else seeing this?  I need more reports of the problem so I can figure out what is the common factor...

Offline

 

#3 2007-04-10 16:43:39

sheeepguy
Member
Registered: 2011-06-05
Posts: 13

Re: Lockup when scanning in v0.616?

In v0.616 I am not getting a 'lock-up' message but I am getting an error message; "Microsoft Access has stopped working... etc'
I am trying to scan 40k+ and this message first occured after processing 3,896 files. Subsequent scans cause the same error message without processing anymore files. This is a new MP3 Boss install on Vista running dual core and 2 gigs ram.

Offline

 

#4 2007-04-11 01:13:03

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Re: Lockup when scanning in v0.616?

1) Before starting MP3-Boss, rename the files FORM.BMP, CANVAS.BMP and DIALOG.BMP (in c:\program files\mp3boss) to FORMx.BMP, CANVASx.BMP and DIALOGx.BMP.  This will get rid of the background images in the forms.  My guess is that you don't actually have to rename CANVAS.BMP (that is the blue background around the startup switchboard).
2) Now scan...does this eliminate the crash?

I'm making the background selectable (and off by default) in the next revision (v0.617).  I'm also making the number of files to scan at a time selectable (and the default will be 10K instead of the current 15K -- a bit more conservative, although I don't think it is necessary <see below>).

It looks like not everyone sees this problem.  It actually seems to be more of a problem on the higher-end computers than on the lower end.  Form bitmaps have always been a problem with Access...but I thought that problem went away once you moved past about 16MB-32MB total RAM.  However it could easily be due to your printer driver:
http://support.microsoft.com/kb/165985

It is also possible that there are GDI leaks if you are running on WinXP SP2:
http://support.microsoft.com/?kbid=319740

Finally, there is a bug in v0.616 (that is fixed in v0.617) -- if you move the animated horse cursor off the scanning form a lot (so it keeps changing from the horse to hourglass), you lose GDI resources.  Do it 100 times, and that could crash the system.

To take a look at your GDI resources (which is most likely the cause of the crash):
Open your Task Manager (Right-click in an empty part of the Windows Taskbar, and select Task Manager.  Or,  press Ctrl-Alt-Delete to bring it up).  In the Task Manager, click the View/Select Columns menu item -- and make sure you've selected "GDI Objects".  Now, when you look under "Processes" -- find msaccess.exe and take a look at the GDI Objects column -- a normal scan probably has 300 - 700.  If the number gets above 5000, you are probably heading for a crash (10,000 is the absolute maximum for any process).  The most important thing is that you shouldn't see the number continuing to climb upwards. 

In v0.617, I've been spending a lot of time on this (since now the scan can be much larger -- since it is searching for so many filetypes!).  My guess is that you'll be able to use the form backgrounds in v0.617 because of the changes -- here, even in debug mode I've had no problem scanning huge numbers of files.

If you take a look at GDI Objects -- I'd like to know what you are seeing during the scan.

Thanks for your help, and PLEASE keep the reports coming in!

Offline

 

#5 2007-04-11 16:10:06

sheeepguy
Member
Registered: 2011-06-05
Posts: 13

Re: Lockup when scanning in v0.616?

Renamed the three *.bmp files.
Whilst scanning (1st stage - new files check) GDI Objects is fixed on 537 (memory fluctuates around 29,000k).
Creating file list runs fine (and 537 shows in the task manager).
After the file list creation has finished I get this error message; "Microsoft Access has stopped working".(GDI Objects now show as 564).
Files that help describe the problem:
  C:\Users\kiwi\AppData\Local\Temp\WERF315.tmp.version.txt
  C:\Users\kiwi\AppData\Local\Temp\WER964.tmp.appcompat.txt
  C:\Users\kiwi\AppData\Local\Temp\WERB0A.tmp.mdmp

C:\Users\kiwi\AppData\Local\Temp\WERF315.tmp.version.txt;
Windows NT  Version 6.0 Build: 6000
Product (0x3): Windows Vista (TM) Home Premium
Edition: HomePremium
BuildString: 6000.16386.x86fre.vista_rtm.061101-2205
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1033


C:\Users\kiwi\AppData\Local\Temp\WER964.tmp.appcompat.txt;
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="msaccess.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="Msaccess.exe" SIZE="3031040" CHECKSUM="0x3BD9B61B" BIN_FILE_VERSION="8.0.0.5903" BIN_PRODUCT_VERSION="8.0.0.5903" PRODUCT_VERSION="8.0.5903"

FILE_DESCRIPTION="Microsoft Access" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Access" FILE_VERSION="8.0.5903" ORIGINAL_FILENAME="MSACCESS.EXE"

INTERNAL_NAME="MSACCESS" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1991-1997.  All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1"

MODULE_TYPE="WIN32" PE_CHECKSUM="0x2E4F5A" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.0.0.5903" UPTO_BIN_PRODUCT_VERSION="8.0.0.5903" LINK_DATE="09/03/1998 04:06:26"

UPTO_LINK_DATE="09/03/1998 04:06:26" EXPORT_NAME="msaccess.exe" VER_LANGUAGE="Language Neutral [0x0]" />
    <MATCHING_FILE NAME="Msacnv30.dll" SIZE="236800" CHECKSUM="0x61FDBE6A" BIN_FILE_VERSION="3.0.0.0" BIN_PRODUCT_VERSION="3.0.0.0" PRODUCT_VERSION="3.00"

FILE_DESCRIPTION="Microsoft Access" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Access" FILE_VERSION="3.00" ORIGINAL_FILENAME="MSACNV30.DLL"

INTERNAL_NAME="MSACNV30" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1991-1995" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN16"

16BIT_DESCRIPTION="Microsoft Access Basic Code library, Version 2.00, Copyright (c) 1987-1993 Microsoft Corp." 16BIT_MODULE_NAME="MSACNV30" UPTO_BIN_FILE_VERSION="3.0.0.0"

UPTO_BIN_PRODUCT_VERSION="3.0.0.0" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="Msacnv30.exe" SIZE="102400" CHECKSUM="0x23890D81" BIN_FILE_VERSION="3.0.0.2" BIN_PRODUCT_VERSION="3.0.0.2" PRODUCT_VERSION="3.00.0002"

FILE_DESCRIPTION="Microsoft Access" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Access" FILE_VERSION="3.00.0002" ORIGINAL_FILENAME="MSACNV30.EXE"

INTERNAL_NAME="MSACNV30" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1991-1995" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN16"

16BIT_DESCRIPTION="EB Dumb Shell" 16BIT_MODULE_NAME="DSHELL" UPTO_BIN_FILE_VERSION="3.0.0.2" UPTO_BIN_PRODUCT_VERSION="3.0.0.2" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="Msaexp30.dll" SIZE="168448" CHECKSUM="0xE37704CE" BIN_FILE_VERSION="8.0.0.3501" BIN_PRODUCT_VERSION="8.0.0.3501" PRODUCT_VERSION="8.0.3501"

FILE_DESCRIPTION="Microsoft Access Expression Builder DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Access" FILE_VERSION="8.0.3501"

ORIGINAL_FILENAME="MSAEXP20.DLL" INTERNAL_NAME="Expression Builder" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1993-1996. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0"

VERFILEOS="0x10004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2D3C2" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.0.0.3501" UPTO_BIN_PRODUCT_VERSION="8.0.0.3501"

LINK_DATE="11/01/1996 18:07:01" UPTO_LINK_DATE="11/01/1996 18:07:01" EXPORT_NAME="msaexp30.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="Msain800.dll" SIZE="507904" CHECKSUM="0x1B72A95B" BIN_FILE_VERSION="8.0.0.3511" BIN_PRODUCT_VERSION="8.0.0.3511" PRODUCT_VERSION="8.0.3511"

FILE_DESCRIPTION="Microsoft Access International DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Access" FILE_VERSION="8.0.3511"

ORIGINAL_FILENAME="MSAIN800.DLL" INTERNAL_NAME="MSAIN800" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1991-1996. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0"

VERFILEOS="0x10004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.0.0.3511" UPTO_BIN_PRODUCT_VERSION="8.0.0.3511"

LINK_DATE="11/11/1996 20:07:02" UPTO_LINK_DATE="11/11/1996 20:07:02" VER_LANGUAGE="Language Neutral [0x0]" />
    <MATCHING_FILE NAME="Soa800.dll" SIZE="207360" CHECKSUM="0xF26C339D" BIN_FILE_VERSION="8.0.0.3501" BIN_PRODUCT_VERSION="8.0.0.3501" PRODUCT_VERSION="8.000.3501"

FILE_DESCRIPTION="MSAPP Export Support for Microsoft Access" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Access" FILE_VERSION="8.000.3501"

ORIGINAL_FILENAME="SOA800.DLL" INTERNAL_NAME="SOA800" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1996" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2"

MODULE_TYPE="WIN32" PE_CHECKSUM="0x3F637" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.0.0.3501" UPTO_BIN_PRODUCT_VERSION="8.0.0.3501" LINK_DATE="11/09/1996 01:19:42"

UPTO_LINK_DATE="11/09/1996 01:19:42" EXPORT_NAME="SOA800.dll" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="ntdll.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="ntdll.dll" SIZE="1162656" CHECKSUM="0x8FD38B20" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386"

FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)"

ORIGINAL_FILENAME="ntdll.dll.mui" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004"

VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x128171" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386"

LINK_DATE="11/02/2006 09:43:37" UPTO_LINK_DATE="11/02/2006 09:43:37" EXPORT_NAME="ntdll.dll" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="874496" CHECKSUM="0x8440BFFC" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386"

PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System"

FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved."

VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD9614" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386"

UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:24" UPTO_LINK_DATE="11/02/2006 09:42:24" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States)

[0x409]" />
</EXE>
</DATABASE>



C:\Users\kiwi\AppData\Local\Temp\WERB0A.tmp.mdmp;

I cannot open 'WERB0A.tmp.mdmp'. This file is 1.826kb; I'll happily email it to you if you need it.


Printer driver can't be a problem as I haven't installed a printer.
Mp3 Boss was installed as the first of my 3rd party applications (heck I can't live without MP3 Boss) and there are no versions of MS

Office/Access installed.

If I run a scan on a smaller folder (approx 800 files) MP3 Boss works perfectly.

Hope the above helps.

Sheeepy

Offline

 

#6 2007-04-11 18:19:47

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Re: Lockup when scanning in v0.616?

Please send me that file so I can take a look.

Also send me the mp3boss install.log, and any LOG files in your mp3boss directory.

Thanks,
John

Offline

 

#7 2007-04-11 23:02:03

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Re: Lockup when scanning in v0.616?

The install.log looked fine.  I didn't see anything obvious in the other file -- although perhaps it indicates that the error was due to a form closing unexpectedly.  Did the error occur while you were opening/closing forms, or was the system just sitting there scanning?

Rename HORSE.ANI (in the mp3-boss directory) to HORSEx.ANI before scanning the next time.

The next revision should be out in a week or so (I think first as a beta).  It will offer a few advantages to you:
1) It fixes a crash caused by ANY directory path that you have that is over 240chars (is this possibly the problem?)
2) It lets you decide whether to use the form pictures (although it looks like that isn't the problem).
3) It fixes the cursor problem
4) It makes the files-to-scan selectable -- as low as 500 per segment -- and it looks like this at least would probably fix your problem (although it would take longer to scan).
5) It fixes a number of field-too-short errors (although I don't think it is likely this is the problem...since they shouldn't give you an Access error).
6) I've also updated the way the titlebar is handled.  WinXP (only) had a problem with the Access updates the titlebar.  In v0.617, I've switched to an API call that fixes the WinXP problem (and my guess is this will work better for VISTA too).

What operating system does MP3-Boss show in "Help/About MP3 Boss"?  How much physical & virtual memory?

Offline

 

#8 2007-04-12 01:21:40

sheeepguy
Member
Registered: 2011-06-05
Posts: 13

Re: Lockup when scanning in v0.616?

I have left the scan to run unattended on a couple of occasions with the same error.
The 240 chars could possibly be the problem, but wouldn't this have shown in previous versions whilst running winxp (I have successfully scanned the same number of files on my desktop and my previous laptop after reformatting).
Without going through my 3,500 music directories, how can I check if any file path exceeds 240 chars.

About box details;
Operating system: Windows XP version 6.0, Build 6000
2,094mb physical memory (948mb available)
2,097mb virtual memory (1,902mb available)
Network detected,

Will rename 'horse.ani' and let you know what happens
cheers

Offline

 

#9 2007-04-12 04:06:57

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Re: Lockup when scanning in v0.616?

You are probably right that WinXP would have crashed due to the 240 chars -- but it is always possible that the Vista installation has created some longer paths.  It is pretty unusual to have such long paths though...

It's also strange that you don't crash every time -- and not sure why you'd crash after different numbers of files are processed.  What was the max/min processed during a scan?  Anything different running when 9500 files scanned OK?

Is it possible to do a screen capture of the crash and send it to me?

I'm interested in your results after you rename the ani file.

Offline

 

#10 2007-04-12 16:12:58

sheeepguy
Member
Registered: 2011-06-05
Posts: 13

Re: Lockup when scanning in v0.616?

I renamed 'horse.ani' and scanned the entire directory (42,000+) and I got the same error message as previously.
I have sent you a screen capture.
I scanned a folder and sub folders which had 1100 files and it worked perfectly.
In summary, I have succesfully scanned folders which have contained anything from 5 files to 9500 files.
I have never managed to scan the entire drive after trying around 10 times.
All the scans have been done with nothing else running.
Hope this helps.

Offline

 

#11 2007-06-17 05:22:54

mccaffjt
Admin
Registered: 2011-06-05
Posts: 1295
Website

Re: Lockup when scanning in v0.616?

Is everything working fine now under v0.6202?

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2008 PunBB