I have a similar lockup error on the same version.  I can operate within the tool but if i open project metadata components it says downloading components then locks up; see attached.   The org has about 9500 reports.   Smaller orgs with less items the project metadata components opens correctly. 

Note if i build a new project aginst the same org, the wizard works properly, but then once the project is created open projtect metadata does not work.

Bill, maybe if you remove the reports and dashborads from your project using explorer maybe you will be able to open the project.

Windows 10, 16g i7 

Hi Bill, bvanburen,

It seems to us that you have different issues.

Bill, in your case it seems to be an error in the loading process - either something is wrong with the data retrieval on project open (we request some data on the project load) or there's something wrong with the code parsers that are executed on the project load. Can you please send us a bug report from the IDE, so we will have logs to analyze?

You can do this from the Main Menu -> Help -> Report a bug, and please leave checkbox to include your logs enabled. After that we'll get back to you as soon as possible with at least a workaround how to resolve this situation, while we'll work on the fix.

bvanburen, in your case it might be a rendering issue for such big number of files - the UI thread might just lockout, but also we can't be sure in the reason (and how to solve the issue) without the log files. Can you please also follow the same procedure as described above and send us log files so we can investigate what exactly happens?

Thank you for your assistance and looking forward to analyzing your log files :)

Best regards,

Vladimir

Hi Vladimir,

Thanks for your reply.  As I mentioned in my orignal post, TWS locks up when I open this large solution and nothing works.  When I click on anything, nothing happens.  I can't even exit TWS (I have to kill it in Windows Task Manager).

Is there some other way we can generate a log file?

Thanks,

Bill...

Hi Bill,

You can find the first log file in the '%ProgramData%\TheWelkinSuite\Application' folder with the 'TheWelkinSuite.log' name.

The second log file is located in the '%AppData%\Microsoft\AppEnv\12.0' folder and is called 'ActivityLog.xml'.

Please send both files to info@welkinsuite.com and we'll get back to you with the results.

Thank you once more for your cooperation!

Vladimir

Hi there,

I've got the same issue with Blaze R7: I have a project connected to a large org, during last session I've left the Account.object open, and now if I open the project it hangs indefinitely. The top status says "Solution loaded" but everything is locked and I have to kill the process. Account has got around 780 fields.

Thank you for advising,

Francesco 

Hi Francesco,

Thank you for getting to us with this issue. Unfortunately it seems that the fields editor in it's current state won't handle properly so heavy object. The main reason in it is the rendering of all of the controls - it's a bit weird in Mono Framework.

It is one of the top priorities for us at the moment to change to the native Mac OS rendering approaches to increase the performance of the heaviest views - FLS, Fields, Layouts, Local History. We believe that once done this will allow productive work even with such big objects as in your case.

As I understand your project is right now 'locked' by the fact that the IDE tries to open the Account object on loading the project - the workaround might be to find a '%ProjectName%.userprefs' file in your project's directory and remove it. Once this is done - the IDE won't try to open files when you'll open this project.

Thank you,

Vladimir 

Hi Vladimir,

thank you for the advice, I discovered it already. Unfortunately it's not possible to use TWS on such heavy orgs at the moment, because of this ticking bomb like whenever I open one of the views you mentioned, it hangs indefinitely. I appreciate that you're on it though. There are other things that I'd like to see improved, but certainly this is the top priority on Mac version right now.

Best,

Francesco

Hi Francesco,

I understand the lack of comfort in such situation, however you can still keep coding - all our code editors support really huge files and working without any issues on 10k+ lines of code.

We'll do our best to resolve this issues as soon as possible!

Best Regards,

Vladimir

Hi Vladimir,

situation is indeed improved with Blaze R10: keep it going!

Thank you,

Francesco

Hi Francesco,

Thank you for your feedback!

We will keep working on this.

If you would be faced with similar cases, please let us know so that we cover all of them.

Regards,

Kate