Unending "Preparing Project data..."

[alastajj]

When previewing (F4), randomly it shows this message, then you click "okay" and it gets stuck

I'm not sure the cause, it just decided to happen randomly. Only option was to close without saving.

Perhaps a way to "cancel" the "preparing" window could help.

Using latest stable. It didn't happen for me in the previous stable.

#8366

(I use a blank chrome install so there's no extensions etc.) I pressed F12, but I don't know what or if any of this helps:

[alastajj]

I saw someone else mention they had this issue too, from Jan 10th:

This has been happening more and more often when starting preview - it gets stuck on this screen loading back and forth. I lose everything that was not saved. Any advice?

[CrackHub]

Next time you can try pressing "Ctrl + S"

[AshleyScirra]

I'm afraid as per the bug report guidelines, without a sample project and steps to reproduce it is pretty much impossible to investigate this. Can you provide that?

[indyClubGames]

My steps to reproduce it are pretty random. It seems most common when making a change to the project and previewing soon after but at other times it seems quite random.

If I need to I can send my project to you Ashley, where would you prefer the PM?

I get solving the crash would be a priority but even without solving the crash PLEASE make a (X) on the preparing project data operation so we can cancel it when it goes into an infinite loop and then save the project. I would save before every preview but each save takes about 30 seconds and I preview a lot.

This was the end of my console the one time it showed up after crash.

[indyClubGames]

More hopefully helpful information: Saving right before previewing also seems to increase the chances of this happening. If it happens and you click control+s it will close the never ending bar and actually save! (Thank you CrackHub!) However, when you preview again it will have the same issue so you have to reset the editor before previewing again.

[RabloGames]

If it can help, here's the link to my post about the same problem. I tried to describe it as much as possible.
#8366

However, I never had the problem again since I wrote that post. It happened to me maybe 4 times in total.

[indyClubGames]

Thanks for the new information Rablo!

It seems to be quite related to making image adjustments before previewing. It has been happening to me on average once every 2 to 3 hours of construct editing. (I do a lot of image adjustments and have tons of them)

[AshleyScirra]

By far the best way to deal with an issue like this is to make a dummy project filled with whatever is necessary to reproduce the problem, and share that here. This is always the quickest and most reliable way to get problems fixed.

If you cannot do that, you can try sending your full project to me at [email protected] where I will take a look, but in general if I follow your provided reproduction steps 10 times and the problem doesn't happen, then it's infeasible to investigate any further. Beyond that we can try making random changes and rely on hope and luck, but that could either take a very long time (months or years), or never find a solution. So as I said, it is far preferable to try to find a way to reproduce this with a public project (as per our usual bug report guidelines, as that is always the case, no matter the bug).

[EMI-INDO]

I triggered the above issue with steps

Inspect using Browser Developer Tools (F12/Ctrl+Shift+I).

• Enable Addon Dev mode in the C3 Editor.
• Start the local server for the addon.
• Add the local addon URL to the C3 Editor Addon Dev.
• Reload the browser.
• Create a new project, add the addon, and save it.
• Reload the browser again.
• Reopen the project and review it.
• Inspect using Browser Developer Tools (F12/Ctrl+Shift+I).

If you don't find the problem, merge the 3rd party addon sdk V1 and V2 in 1 project.

• VIDEO: https://drive.google.com/file/d/1oWqQbcc8OpmZITs__9UBGtilYl7EMpVo/view

Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' blob: https://downloads.construct.net https://downloads.scirra.com". Either the 'unsafe-inline' keyword, a hash ('sha256-il9OJHbmCgFaRYhKbZS3ooHm871iiFcBpLCQwsSsuRY='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

main.js 145

• resource blok code

nea = function(d, e, f) {
    CCG.fd.C(e);
    CCG.fd.Wa(f);
    return CCG.fd.Go( () => {
        d.Pg = (new DOMParser).parseFromString(e, f || "text/xml");   // line
        d.lg = new CCG.fd.nn.Element(d.Pg.documentElement,d.Pg);
        return d
    }
    )
}

[AshleyScirra]

@EMI-INDO - the issue originally filed here is about the editor getting stuck on the "Preparing project data..." dialog. Your comment appears unrelated to this. Further I believe the "Refused to apply inline style..." error in the console is a false positive, doesn't affect anything, and can be ignored. The only console message that appears to be related to the actual problem appears to be the "unknown spritesheet" error in the original report, but that gives us very little to go on, and as ever reliable steps to reproduce the issue are the key to solving it.

[EMI-INDO]

All the issues mentioned above do not have a repository (repo).

Unending "Preparing Project data..."
This issue will not always be triggered, there is no definite way to trigger it, and even if it is triggered, it happens randomly. Therefore, they cannot provide a repository.

so I cannot provide a repository either.
However, I can provide the steps to reproduce the log that shows the same issue they encountered.

In essence, the log for all the issues mentioned above can be triggered by following the steps I have described.

I am not experiencing any issues myself.

[EMI-INDO]

• for Error starting preview problem: Error: unknown spritesheet

can't be triggered with a simple project, like it has to use a large project, it will happen randomly