Magento 2 version 2.4.7-p2 “Page Builder was rendering for 5 seconds without releasing locks” error.

[sunit9]

Preconditions and environment

Magento 2.4.7-p2

Steps to reproduce

1. Login to magento admin
2. Content -> Block -> Add new block
3. Add Block Title
4. Add Identifier
5. Click on Save

Expected result

Block should be save successfully.

Actual result

On screen only loader display and in console getting error.
Page Builder was rendering for 5 seconds without releasing locks

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @sunit9. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[Bashev]

looks like same with this: #37516 and #37798

[sunit9]

I have check in firefox but not working.
My chrome version is Version 127.0.6533.119 (Official Build) (64-bit)
I check same things for 2.4.6-p2 and it's working fine.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[medigeek]

I think your problem is with mageno 2.4 and CORS - apache htaccess or nginx requires some tweaking

Check your browser's javascript console log.

Access to script at 'https://example.com/static/versionXXXXXXXXXX/adminhtml/Magento/backend/en_US/requirejs-config.js' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

The solution is explained here:
https://magento.stackexchange.com/a/170726

Had the same issue. The above worked for a support case. Hopefully it will work for you too.

From the magento stack exchange:

I faced the same problem with a Magento setup with Nginx.

I share you my working configuration which solve this CORS problem for an headless Magento use case (API).

[...] (don't do the API location /rest as it may break some sites)

Some Allow-Headers is not mandatory, try to test which are on your case.

Then add headers on all other requests :

location ~ (index|get|static|report|404|503)\.php$ {
    .....
    .....

    add_header 'Access-Control-Allow-Origin' '*' always;
    add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
    add_header 'Access-Control-Allow-Headers' 'DNT,Authorization,X-CustomHeader,Keep-Alive,User-Agent,Origin,Referer,X-HTTP-Method-Override,X-Accept-Charset,X-Accept,Accept,Access-Control-Request-Method,Access-Control-Request-Headers,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type' always;
}

Make sure to keep the always option in order to add these headers for response code other than : 200, 201, 204, 206, 301, 302, 303, 304, 307, or 308

Make sure you do not have basic auth authentication behind. If not, update the configuration in order to allow the OPTIONS CORS request made from your browser.

[engcom-Bravo]

@magento give me 2.4.7-p2 instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://14ab03d38900151067a7d8dc2d86d5f6.instances-prod.magento-community.engineering
Admin access: https://14ab03d38900151067a7d8dc2d86d5f6.instances-prod.magento-community.engineering/admin_90c5
Login: ab3740ba
Password: 79aeae1bb903

[engcom-Bravo]

@medigeek Thanks for your Contribution!!

Hi @sunit9,

Thanks for your reporting and collaboration.

Could you please refer this comment #39076 (comment). which resolves your issue and please let us know if you are still facing any issue.

Thanks.

[sunit9]

I have change in following file
vendor/magento/module-page-builder/view/adminhtml/web/template/page-builder.html

<iframe attr="id: 'render_frame_' + id" sandbox="allow-scripts" style="position: absolute; width:0; height:0; border: none;"></iframe>

To

<iframe attr="id: 'render_frame_' + id" sandbox="allow-scripts allow-same-origin" style="position: absolute; width:0; height:0; border: none;"></iframe>

In sandbox i append "allow-same-origin"

It works for me. I do not have idea it's good solution or not. If anyone know then please advise.