Closed tomkoen closed 6 years ago
@jief666, the problem is that after HFSBTreeNode is destroyed, findHFSPlusCatalogFileOrFolderForParentIdAndName returns invalid data
I'm having a look.
One possible workaround is making the variable global
HFSBTreeNode leafNode;
Yes, yes. I missed that. The funny is that it worked for very big images I'm using to test !
Global ?? No no, we can do better.
The funny is that it worked for very big images I'm using to test !
It could, depends on the compiler...
I have plenty of RAM, so maybe the new allocation didn't go over the old ones, leaving the memory content intact.
I'm a big fan of code quality fan ! So great you caught me.
Here is my solution : #69.
Thanks.
Recent changes by @jief666 broke the code, newly introduced findHFSPlusCatalogFileOrFolderForParentIdAndName returns invalid data.