Crash on scanning too many files ? (1 Viewer)

[Acteo]

Hello,

On startup MPTagThat scans music folder and crashes.
Using Win 7 32
Message "Running out of memory. Scanning aborted."

Thanks for help


Signature du problème*:
Nom d’événement de problème: CLR20r3
Signature du problème 01: mptagthat.exe
Signature du problème 02: 3.0.3.0
Signature du problème 03: 4eb198c4
Signature du problème 04: System.Windows.Forms
Signature du problème 05: 4.0.0.0
Signature du problème 06: 4ba1e14e
Signature du problème 07: 1457
Signature du problème 08: ad
Signature du problème 09: System.InvalidOperationException
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
Information supplémentaire n°*1: 8305
Information supplémentaire n°*2: 8305ada8eaf2b546e34b2fde8daa5483
Information supplémentaire n°*3: db9a
Information supplémentaire n°*4: db9a534e4511428047ce8852505194c3

Lire notre déclaration de confidentialité en ligne*:
Windows 7 Privacy Statement - Microsoft Windows

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion*:
C:\Windows\system32\fr-FR\erofflps.txt

 

[hwahrmann]

Yes, this is a known problem.

Maybe you have selected the "Scan Subfolder" check bos and you are trying now to scan th complete Music collection.
You can cancel the scan by pressing the Cancel button on Bottom Right, just right of the Progress bar.
If you can't reach that, then you need to clean the config folder and start over.

I know already how to fix that, but it takes quite a time, since i need to totally restructure the Grid handling.

 

[Acteo]

Re : Crash on scanning too many files ?

OK
Thanks for the info
Hope you will find the time because this is a usefull application.

 

[jameson_uk]

Don't suppose this is on the radar or you know what needs fixing?

I want to run a script against my whole collection but it just dies. I re-arranged to put into A-Z folders but it is still crashing on a these. I don't fancy running the script manually for 600 artists...

I think this is partly down to me having some large cover art and this is what is eating the memory

 

[hwahrmann]

Tried somehow to fix it in latest version, by using virtual datagrid.
But i still keep a copy of all the tags read in memory, and this causes troubles for large collections.

I'm thinking of implementing some sort of Object Oriented Database, which allows me just reading back the stuff, which i need at time of processing.
But it still needs some investigations and ofc implementation.

 

[jameson_uk]

Are the images loaded into memory too? I have just re-ripped my collection and ended up with a load of 1500x1500 images which appear to be a bigger issue than the tags?

just wondering if I could turn off loading images whether that would help at all??

 

[tourettes]

But i still keep a copy of all the tags read in memory, and this causes troubles for large collections.

32 bit process can access 2GB memory. That is a lot for tags. It would have to be multi TB mp3 collection that creates such amount of metadata), unless abum art is kept in the memory as well. If the album art is kept in menory then it could be easier just to store that into some temp files instead of having to implement full blown object oriented DB for some temporary data.

 

[hwahrmann]

Are the images loaded into memory too? I have just re-ripped my collection and ended up with a load of 1500x1500 images which appear to be a bigger issue than the tags?

just wondering if I could turn off loading images whether that would help at all??

I'm reading all tags, including the Picture or ID3 APIC and keep them in the Tag object, which i create.
So this might be an issue.

Previously i found that the System.Draw methods were the cause of the out of memory issues, when a picture was faulty.
After i converted the image processing to FreeImage, the out of memory issues were gone. At least for that.
But i get it afgain after reading around 3000 - 4000 files.

So it seems to be really memory related.
I will do another round of analyzing using DotTrace Memory.

 

[jameson_uk]

Previously i found that the System.Draw methods were the cause of the out of memory issues, when a picture was faulty.
After i converted the image processing to FreeImage, the out of memory issues were gone. At least for that.
But i get it afgain after reading around 3000 - 4000 files.

So it seems to be really memory related.
I will do another round of analyzing using DotTrace Memory.

I am getting this with less than 1500 files but with a lot of large image files.

 

[Acteo]

Thanks !
This is solved in last version !

Thank you for this great improvement !