> Oh. Did you monitor app? Running out of memory? Yes, and it does not run out of memory (10 600 KB max used)
> Did you try with maybe 2 instead of -1? Tried, but still crashing. In addition, I need to calculate all levels of subfolders. > you could write a debug message before and after the Calculate call to see if > it happens while plugin is running. In the doc, I found the "Close" function for DirectorySizeMBS. Tried it, unsuccessfully. Tried to change the ticks parameter of the CalculateDirectorySizeMBS, tried to set up the Yieldticks parameter, tried to use the class inside and outside a thread. What I noticed is that modifying ticks or Yieldticks parameters changes the delay before crash. And before crashing, the thread was stopped (when in a thread). It seems like the plugin and this function modify something in memory, leading to an access violation more or less quickly after result is returned. The crash often appends as soon as I click on a button, but may happen with no user action (and no MBS plugin call). What could I do to solve this issue? Jean-Luc Arnaud Le 26/01/2015 19:14, Christian Schmitz a écrit : >> Hi all, >> >> Using DirectorySizeMBS as shown in the MBS doc, I get the size of my >> data folder, and then (5-10 seconds later), my app crashes with a >> c0000005 code (Access Violation). > Oh. Did you monitor app? Running out of memory? > >> d= Source.CalculateDirectorySizeMBS(True,6,False,-1) > Did you try with maybe 2 instead of -1? > >> Could this be due to the DirectorySizeMBS function, or am I doing >> something wrong? > you could write a debug message before and after the Calculate call to see if > it happens while plugin is running. > > Sincerely > Christian > _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
