Author Topic: Will not work with over 32786 files!  (Read 14790 times)

Offline KaptnK

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Will not work with over 32786 files!
« on: June 08, 2010, 02:36:48 am »
I found this great sounding product today, but unfortunately it does not seem to work for me. ???

I have 40825 MP3 files I was having it check, but after looking for all the files it conclude that there were 0. From watching the display it appears this is because the counter variable used is a signed short, limiting the number of files this tool can handle to 32786.

Any chance of getting this changed??

Offline Synbios

  • Hero Member
  • *****
  • Posts: 671
  • Karma: +5153/-0
    • View Profile
Re: Will not work with over 32786 files!
« Reply #1 on: June 20, 2010, 03:53:39 pm »
Should be a pretty easy fix in VB, all chip needs to do is declare a larger variable type. I don't know if he's still working on this project, but when he sees this post he can most likely make that update.

Offline Williamsonborough

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Will not work with over 32786 files!
« Reply #2 on: September 02, 2021, 08:35:44 pm »
Is the file XML? Note that a XML parse tree Node object is non-trivial size (it has to keep lists of children, parent reference, a current in-scope namespace list, list of attributes and the value itself, etc). The webM parser doesn’t create a copy of the value, because it points a reference to the input stream data from the parse tree node, so there aren’t two copies of the data in memory during parsing, as with some parsers. But it would not surprise me if a 60M XML file took 600M of RAM once parsed.

Offline shufenghanumn

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Will not work with over 32786 files!
« Reply #3 on: January 16, 2022, 04:39:08 pm »
so thanks you
i learn much from this post!   fnaf