bruce78 wrote: Ok, here's the bug report - bugs.limesurvey.org/view.php?id=11974 . Let me know if I can add anything further...

Did you report the bug to be private? Attached your survey? The ticket seems to be non-accessible for normal users.

jelo wrote: Did you report the bug to be private? Attached your survey? The ticket seems to be non-accessible for normal users.

Yeah, the bug is private and the lss survey file is attached... do you think the bug report it should be available to all users?

The question is if you think it shouldn't.

If the bug is a general bug and there is no private data from your side and no security issue for Limesurvey, I don't see why a bug should be private (if private, only the core LS team can have a look at it, if not private a broader public can see it).

Now if your .lss file contains data that you don't want to make accessible publicly, then go for private.
If you report a security issue, that can be used by others to caus problems, go for private.
So I think only the reporter can decide if private is necessary or not.

Hi Holch,

holch wrote: Now if your .lss file contains data that you don't want to make accessible publicly, then go for private.

Right now there's a lot of private information in the lss file, hence marking the bug report as private.

Do you think it's worth seeing if I can upload another version of the lss file that still has the buggy behavior but that is fine to be in the public domain?

No, I don't think it is necessary. In general I think most bugs are solved by the core team anyway.

holch wrote: No, I don't think it is necessary. In general I think most bugs are solved by the core team anyway.

Ok, thanks Holch. For what it's worth, Denis suggested testing out 2.52+160929 which seems to have resolved it. Load times are around 10 seconds now which is much better!

I've also included copies of the survey running 3 different versions along with approximate loads times on my machine if this is of any relevance...

2.52+160929 - loads in 9 - 10 seconds

2.55.3+161111 - loads in about 30 seconds

2.06lts Build 160801 - loads 13 seconds

I find 9-10 seconds still quite slow, but it seems like a huge improvement over 13 or even 30 seconds.

Yeah, agreed... it may be due to a lot of survey complexity, but I'm not 100% sure...

FYI, there's a fix committed in github here ...

holch wrote: I find 9-10 seconds still quite slow, but it seems like a huge improvement over 13 or even 30 seconds.

Yep, sure.

I think we need to introduce caching in createFieldMap function but before randomization And maybe/.surely some part of EM singleton ...