Skip to main content
Topic: Library Tree Discussion (Read 42230 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Library Tree Discussion

Reply #250
@zoumbro

I'm not keen on debugging old versions of library tree because most releases have various bug fixes, possibly not always evident from the change log. I can't remember if there were any changes that might have affected this. It's also best to use the latest version of spider monkey panel.

In this particular case, it looks as though the library was updating since on_library_items_changed was called. Appearance of the abort message, I think, only has a short delay. From the stack trace, library tree was in the middle of updating the tree.

In general tree updates in response to library changes should be very rapid and occur in the background: only affected items in the tree are altered.

Aborting scripts part way through may give unpredictable results and a script error. What happens if you just let library tree continue and finish? If that's OK, perhaps choose don't ask me again & don't worry about it.

As a test I just tried changing 24,000 tags. All proceeded fine on my device in that scenario. There was no message.

Library Tree also has an option to switch off automatic syncing with the media library: panel properties: "ADV.Library Sync: Auto-0, Initialisation Only-1". If auto-syncing is off the library used by library tree will only be updated on initialisation, view change or through manual refresh on the menu.

I have seen the abort message on a number of occasions when it isn't really the script that's at fault, e.g. if windows is busy (e.g. updating) and necessary files can't be read from the hard drive in a timely way. Then scripts can stall at points difficult to predict and the message can appear.

Re: Library Tree Discussion

Reply #251
Without changing the font size, add line-height setting function?

Re: Library Tree Discussion

Reply #252
See: menu … options > mode > line spacing

Enables line height to be padded as required. I think adding padding is more flexible than setting a fixed line height.


Re: Library Tree Discussion

Reply #254
@WilB

Hello WilB, even with this last version I am getting this error:

Error: Spider Monkey Panel v1.2.2-preview+0db3c6a4 (Library Tree v2.1.2 by WilB)
OrderByRelativePath failed:
allocation size overflow

File: <main>
Line: 542, Column: 61

Stack trace:
  Panel/this.sort@<main>:542:61
  rootNames@<main>:1205:48
  Library/this.getLibrary@<main>:1190:119
  Timers/this.lib/<@<main>:2911:115

Regards,
Andrea

@WilB
Hello WilB, any news about this?
I am still having this blocking error.
Regards, Andrea

Re: Library Tree Discussion

Reply #255
As far as I am aware this seems to be a bug in spider monkey panel and outside of my control, but I am open to suggestions. I just tried again with a 642K test library & all was OK here. That particular error seems to be occurring on panel initialisation and is explicitly related to view by folder structure. So you could try a different view (if the error is locking you out you could open panel properties and find SYSTEM.View By [it's probably the last entry] and change it to 1 to set a different view).

I thought you were debugging the issue with @TheQwertiest? It sounds as though the issue is reproducible and so it ought to be possible to resolve the cause.

HTH

Re: Library Tree Discussion

Reply #256
Hello WilB, thanks for caring about and for the new tips.
I already notified @TheQwertiest of the problem and he promised me a debugging version of SMP that I am still waiting for...
And, moreover, he wrote that the problem was looking to be related to your script...
Now, having your new feedback, I will go back to him again.
Many thanks and kind regards, Andrea

 

Re: Library Tree Discussion

Reply #257
And, moreover, he wrote that the problem was looking to be related to your script...
I've never said such a thing though :\
The problem with `bad_alloc` in `OrderByRelativePath` is most likely a memory exhaustion problem. Theoretically, script could reduce memory usage by operating on smaller arrays or storing less data, but that would greatly increase complexity of the script.

 
SimplePortal 1.0.0 RC1 © 2008-2019