View Issue Details

IDProjectCategoryView StatusLast Update
0020970MMW 5Main Panelpublic2024-06-19 20:47
Reporterzvezdan Assigned To 
Status feedbackResolutionopen 
Product Version5.1 
Target Version5.1 
Summary0020970: Empty Tree panel after restart/changing skin
Description- Create two tabs, one of them having the left side bar with Tree panel displayed and the another tab with the left side bar closed;
- keep the tab with closed side bar active and restart the program or change skin;
- after restart enable View / Left panel -> it will be empty.

If I have just one tab with closed left side bar, after restart and enabling it, it will be displayed fine.
TagsNo tags attached.
Attached Files
Fixed in build


related to 0020975 resolvedpetr Columns are messed up after skin switching / 'Summary' column handled inconsistently 
related to 0020974 closedpetr Uncaught Error: setVisibility called on undefined element! (crash A14A1D9D) 



2024-05-31 18:12

administrator   ~0075665

Hi Zvezdan. I've tried replicating this in any number of ways but haven't been able to. Is this occurring consistently for you? Could it be specific to a certain skin?


2024-05-31 19:54

updater   ~0075672

Last edited: 2024-05-31 19:54

Well, I managed to reproduce it several times with 3027, 3021 and 3005, but now I cannot reproduce it with any of them. It was mostly Material Design.


2024-05-31 20:05

updater   ~0075673

Now I got this, the empty Playing panel after closing it, changing skin and open it. The status bar of Playing panel displays fine. It is restored when I choose Reverse list.


2024-05-31 20:16

updater   ~0075674

And one new anomaly, the Source and Summary columns are messed up, It would be too much if I start reporting all of this as new issues.

By the way, I managed to get the empty Tree panel again, I am trying now to reproduce it with Flat Monkey. It seems it happens after changing order/width of columns.
Columns meesed up.png (71,845 bytes)   
Columns meesed up.png (71,845 bytes)   


2024-05-31 20:30

updater   ~0075675

Yep. Here it is again with Flat Monkey. I just played a little bit with the width of columns and switched Source and Summary columns, then closed left side bar, restarted the program and opened the side bar.

Note that Source and Summary columns again switched their positions. And that is happening with other columns as well, so I will open the new issue for that, if it is not already reported.


2024-05-31 21:24

updater   ~0075676

This happens even with one tab, but only with Material Design and Flat Monkey, regardless of the chosen size in skin. I cannot reproduce it with other skins, even with those that have size as an option.

I think I could reproduce it always. I just need to change width of any column before closing the left side bar and restarting the program or changing the skin (only between MD and FM).

And one more screenshot with messed up columns, this time Title and Summary.
Columns meesed up 2.png (58,568 bytes)   
Columns meesed up 2.png (58,568 bytes)   


2024-05-31 21:59

updater   ~0075678

Last edited: 2024-05-31 22:03

It seems this issue is not happening when the left side bar has just the Tree panel or together with Lyrics panel, but only in combination with Preview panel. Also, it doesn't matter if Preview panel is above or below Tree panel, or which layout it has (Advanced, Side by side).


2024-06-04 17:00

administrator   ~0075727

Hi Zvezdan. I still can't replicate this issue (blank tree). But I'm beginning to wonder whether this issue only occurs once 0020975 has been triggered. So can I ask, if you do a clean install, are you able to replicate this bug if 0020975 (columns messed up after skin change) hasn't occurred?


2024-06-04 19:52

updater   ~0075741

I don't know what you meant by "do a clean install". I cannot test it without my old database file since it contains albums.

I tried with the clean Portable folder with just registry and ini files from the old installation added, and then I selected folder with albums in the Folders branch, but I cannot reproduce the issue in that case.


2024-06-04 20:59

administrator   ~0075749

I mean:
1 Clean portable install
2 In the wizard, scan 1-2 directories (e.g. with a few albums) so you have some test data
3 Attempt to replicate bug
 a) first without replicating 0020975
 b) then after you've replicated 0020975

That should let us know whether:
- the bug is somehow related to your DB
- the bug is dependent on columns getting corrupted


2024-06-08 19:48

updater   ~0075841

Last edited: 2024-06-08 19:59

It happens after restart, unrelated to the changes of column width as it was previously. However, in this case I think it is related to the 0020962 issue, since I noticed it several times when inline edit didn't accept keystrokes, but maybe that was just a coincidence. It is not always empty when keystrokes are not accepted, I could reproduce the bug with keystrokes more often.

Also, unlike previous tests with changed column widths, this one happens even when the left side bar contains only Tree panel, without Preview.

- Cleaned Portable folder, copied registry, ini and db files from the previous installation;
- started program, Playing node selected, all panels closed, restarted program;
- opened auto-playlist editor and tried to change its name -> doesn't accept keystrokes;
- opened left panel -> it was empty.

Anyway, here are video and log files for both issues.


2024-06-09 14:01

updater   ~0075846

I was wrong. It is not related to the 0020962 issue. It just happened when inline edit accepted keystrokes. I tried the same steps as on the last video, opening auto-playlist editor after restart. However, I made this test with the cleaned Portable folder, i.e. empty db, ini and peristent.json. Although. I must say it happens very rarely, maybe 1 in 10.


2024-06-11 21:04

developer   ~0075908

Last edited: 2024-06-11 21:05

@Zvezdan: I am also unable to replicate and the log does not show much..

But I wonder if you right-click the empty area => Inspect element
what does it show? Is the 'MediaTree' element there (like on my screenshot)?
Or is it just set to invisible (style display:none) ?
image.png (169,174 bytes)   
image.png (169,174 bytes)   


2024-06-11 22:34

updater   ~0075913


2024-06-12 14:52

developer   ~0075923

Hmm, the lvViewport includes just the MenuButton and no nodes for some reason.. :-/
@Zvezdan: Is this always reproducible in your portable install?
If yes, then zipping and sharing whole portable folder with me could help me to replicate and fix the issue?
Or maybe sharing just persistent.json and MediaMonkey.ini could be enough to replicate..


2024-06-12 15:05

updater   ~0075928

It is more questionable why the lvViewport has 0 x 0 size, even having just that button. As you could see from these screenshots, that button is also invisible.

It is "reproducible", but very rarely. It took me about an hour and 20 restarts to reproduce it, so it is really no joy doing that. I think that I had more success reproducing it with the first described procedure (changing column widths), then the last one with a new autoplaylist.

I don't think there is a need that I send you Portable folder. As I said, the later test with autoplaylist is with the cleaned Portable folder, i.e. empty db, ini and persistent, only copied registry from previous installation.


2024-06-12 16:55

developer   ~0075934

Last edited: 2024-06-12 16:55

ok, so I will keep trying to repro and make a code review and hopefully will find the cause..


2024-06-14 10:47

developer   ~0075955

@Zvezdan, could you please replace your current /controls/listView.js by this one:
and test whether it resolves the issue?


2024-06-14 12:16

updater   ~0075958

Last edited: 2024-06-14 12:25

I will keep trying, but as I said, it happens very rarely, it is hard to reproduce. I could try it for an hour, and if it doesn't happen in that period, that still is not telling for sure that it is fixed.

However, I am wondering if this issue has anything related to another similar issues with empty panels:
- Playing panel, reported in this thread (;
- Preview and/or Lyrics, which it seems is fixed (

Maybe I could try to write an AutoHotkey script to somehow automate testing, but I need some kind of detection when the issue happens.