Accessing "edit menu | settings" freezes program (1.0.3)

[pauljs75]

It might not specifically be a problem with LMMS code, but I do suspect a problem with a dependency on some library file not included with the program in the Win32 build. (Program looking for something not there and getting stuck when it needs it. Also would explain why this happens for some people and not others.)

I'm not a programmer, but shouldn't there be error trapping for cases like this? (Return error message "such and such .dll not found", stop trying to use whatever it was looking for, and let user get on with business.)

Oldest version I had where this freezing wasn't a problem was 0.4.13. (Which is why I've held onto it for so long.)

[musikBear]

thats on your win x32 -right? I cant reproduce on 1.092, and i can see that i tested this, when i did tests on 1.03, so at least then, there was no issues Poul, you have had some weird hickups. Perhaps something is lurking somewhere on your install? I have also tried to delibrately mess the install up, by removing the configfile, and 1.092 nicely recreate this missing file (obs all user choices are ofcause lost) -but lmms loads correctly, and works correctly. I think you have some other issue on your pc.

[kmouse]

I've got a similar problem on my copy of LMMS. Some actions I perform freeze the program for about 12 seconds, which happens every few minutes so can get quite annoying. Often it'll happen when I'm looking through the "My projects" bar on the side, and almost every time when I click the setting button on an instrument () I'm using LMMS 1.0.93 but it also happened on 1.0.92. All other versions have worked fine so I'm not sure where the problem is.

[tresf]

The file navigation slowness can certainly be caused by the OS, especially certain antivirus programs. I have this issue with a Windows 8 x64 computer with McAfee antivirus installed. I too would like to know the underlying cause of the latency in file navigation but nothing obvious stands out.

[musikBear]

one thing i know is that zasfx maps all drives. This had emence influence for a guy that had lmms on a somewhat bulgy network . (28 drives!) All i/o opps started to take much more time when we left the 0.14 series. But there was so much sucker on that cake, so a few secd waiting for os i/o was nothing (imo) And i think its important that accessing assets inside lmms (sidebar assets iow), is fast, it is when the OS gets involved, and needs to traverse folder/ volumes -Then a significant delay ..or 'lag' if you like, happens before the i/o dialog opens. So its os and not us :) I will test if having zasfx inside a project has any influence, but after the initial load, i would doubt that.

---

There is no difference. ~ 8 secd to access the OS dialogs, nomatter what plugins used, or size of the project

[eagles051387]

I might have another way to potentially eliminate the os using some AI searches that could help speed up the asset access in that side bar.

On Tue, Aug 19, 2014 at 1:13 PM, musikBear notifications@github.com wrote:

one thing i know is that zasfx maps all drives. This had emence influence for a guy that had lmms on a somewhat bulgy network . (28 drives!) All i/o opps started to take much more time when we left the 0.14 series. But there was so much sucker on that cake, so a few secd waiting for os i/o was nothing (imo) And i think its important that accessing assets inside lmms (sidebar assets iow), is fast it is when the OS gets involved, and needs to traverse folder/ volumes -Then a significant delay ..or 'lag' if you like, happens before the i/o dialog opens. So its os and not us :) I will test if having zasfx inside a project has any influence, but after the initial load, i would doubt that.

— Reply to this email directly or view it on GitHub https://github.com/LMMS/lmms/issues/1069#issuecomment-52619179.

Jonathan Aquilina

[tresf]

Johnathan, please do.

[pauljs75]

Short vid showing what's going on: http://youtu.be/37K0u8igMBY

As a user though it still isn't exactly obvious as to why this is happening. I can only take guesses based on some things which have happened with other software and how they got resolved. (Missing DLLs, having to install some version of MSVC or Net that wasn't on the computer, etc.)

[tresf]

Still unable to reproduce.

Can you reboot to make sure none of the files are in use then uninstall.

Next, rename the following directories/files: %programfiles%\lmms %userprofile%.lmmsrc.xml %userprofile%\lmms

Next, reinstall and post your progress.

https://cloud.githubusercontent.com/assets/6345473/3991892/0879ed8a-28ed-11e4-9c4a-cf417f5fbcd2.png

[tresf]

@pauljs75, please perform the recommended steps above. If they do not resolve it, it is likely you will need a tool to do some forensics such as process explorer to get to the bottom of this.

Since no one else can reproduce the only other option is to take a P2V of your PC using VMWare Converter and ftp it to me where I can reproduce this from my end. Otherwise, this will be closed as "can't reproduce".

[badosu]

@pauljs75 A long time has passed since this issue was reported...

Could you try this on the most recent version of lmms (1.1.0)?

[tresf]

Agreed. Closing. He can reopen if needed. Thanks for the bump @badosu .