Make WordPress Core

Opened 2 months ago

Closed 2 months ago

#65575 closed defect (bug) (reported-upstream)

Chrome crashes when opening Themes in WordPress Playground

Reported by: dharmikpatel97 Owned by:
Priority: normal Milestone:
Component: Administration Version:
Severity: normal Keywords:
Cc: Focuses:

Description

Hi team,

I'm facing an issue in WordPress Playground. Whenever I click Appearance → Themes, the Chrome tab crashes and shows "Aw, Snap! STATUS_BREAKPOINT".

I tested it multiple times and the issue happens every time.

I'm using the latest version of Google Chrome on Windows 10.

I've attached a screenshot for reference.

Thanks!

Attachments (5)

bug.png (21.5 KB ) - added by dharmikpatel97 2 months ago.
chrome-status-breakpoint.png.png (31.4 KB ) - added by sachinrajcp123 2 months ago.
edge.png (66.8 KB ) - added by sachinrajcp123 2 months ago.
opera-page-crashed.png.png (68.7 KB ) - added by sachinrajcp123 2 months ago.
firefox-themes-working.png.png (140.0 KB ) - added by sachinrajcp123 2 months ago.

Download all attachments as: .zip

Change History (13)

@dharmikpatel97
2 months ago

#1 follow-up: @sachinrajcp123
2 months ago

  • Keywords needs-patch added
  • Resolutioninvalid
  • Status newclosed

I tested this issue again in multiple browsers.

Steps to reproduce:

  1. Open https://playground.wordpress.net
  2. Go to wp-admin
  3. Open Appearance → Themes

Result:

  • Google Chrome crashes with “Aw, Snap!” and error code STATUS_BREAKPOINT
  • Microsoft Edge crashes with “This page is having a problem” and error code STATUS_BREAKPOINT
  • Opera also crashes
  • Firefox opens the Themes screen successfully and does not crash

Chrome version: 149.0.7827.201
Operating system: Windows NT 10.0.26200

Chrome uploaded crash report ID: CrashID=bp-2362e78b-ed04-4ba5-8271-411f60260702

Edge crash details:
Bucket ID: 52dd4a00c7bd2bf02cbfd5445e16075d
Status: Reported

Based on this testing, the issue appears to affect multiple Chromium-based browsers, including Chrome, Edge, and Opera, while Firefox works correctly. This suggests the issue may be related to WordPress Playground running in Chromium-based browsers rather than a normal WordPress Core Themes screen issue.

I was not able to attach all screenshots here, but I have screenshots available for Chrome, Edge, Opera, and Firefox if needed.

Last edited 2 months ago by sachinrajcp123 (previous) (diff)

#2 @sachinrajcp123
2 months ago

  • Resolution invalid
  • Status closedreopened

Sorry, I accidentally changed the ticket status to closed/invalid and added the needs-patch keyword.

Please ignore that change. I did not intend to close this ticket or mark it as invalid.

This issue is still reproducible in Chromium-based browsers, and I am only adding reproduction details, browser test results, and crash information. I am not attaching a patch because this does not appear to be a confirmed WordPress Core code issue yet.

@sachinrajcp123
2 months ago

#3 @sachinrajcp123
2 months ago

I have attached the additional screenshots for reference:

  • Chrome crash screenshot with STATUS_BREAKPOINT
  • Edge crash screenshot with STATUS_BREAKPOINT
  • Opera page crashed screenshot
  • Firefox Themes screen working successfully

These screenshots support the earlier browser testing results.

#4 in reply to: ↑ 1 @dharmikpatel97
2 months ago

Thanks! If possible, please don't use AI tools for replies. A genuine response based on your own investigation would be much more helpful.

#5 @sachinrajcp123
2 months ago

Thanks, understood. I tested this manually in Chrome, Edge, Opera, and Firefox, and I’ll keep future comments more direct and focused only on what I personally verified.

#6 @dharmikpatel97
2 months ago

I appreciate you verifying it manually and keeping the discussion focused on your own testing. That makes it much easier to investigate the issue.

Last edited 2 months ago by dharmikpatel97 (previous) (diff)

#7 @mukesh27
2 months ago

  • Focuses ui accessibility administration removed
  • Keywords needs-patch removed
  • Milestone Awaiting Review

https://playground.wordpress.net/ is developed and maintained in the https://github.com/WordPress/wordpress-playground repository.

Please open this issue in that repository instead. Since this isn't a WordPress Core issue, I'm closing this ticket.

#8 @wildworks
2 months ago

  • Resolutionreported-upstream
  • Status reopenedclosed
Note: See TracTickets for help on using tickets.