1935880 - Firefox freeze or crash when Hatena blog preview

Status: UNCONFIRMED

(Core :: DOM: Service Workers, defect, P2)

Description

[akihiko.kigure]

Attachment: bugzilla-report.zip

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:133.0) Gecko/20100101 Firefox/133.0

Steps to reproduce:

Reproduction steps

1. Start Firefox and open three windows
2. Items open in Windows
3. Window part.1: 23 tabs
4. Window part.2: 12 tabs
5. Window part.3: 1 tab
6. Edit Hatena Blog
7. Enter text
8. Upload image
9. Save draft
10. Preview

Actual results:

4. When you do 3-3 or 3-4, one of the following occurs
5. It becomes unresponsive
6. It suddenly crashes

Expected results:

A preview of Hatena Blog is displayed.

Comment 1

[Daniel Veditz [:dveditz]]

Did the crash reporter show up, or the "Your tab has crashed" error page? Did you submit the crash reports? It would help a lot to get links to those reports. See https://support.mozilla.org/en-US/kb/mozillacrashreporter

When you do 3-3 or 3-4, one of the following occurs

I don't know what that means. It crashes on step 3 or 4 before you even get to editing the Hatena blog in step 6? Or are you saying that it's only necessary to do 3 OR 4, not both? What window do you edit the Hatena blog in, a 4th window? Or did you mean that if you edit the Hatena Blog in the window from step 3 or 4 it causes the problem, but not if you do it in the window from step 5?

It seems unlikely that a problem editing a blog post depends on the contents of other windows. Maybe it's related to something else like running out of memory? Links to the crash reports would give us clues about things like that.

Comment 2

[Daniel Veditz [:dveditz]]

Do you have to both enter text AND upload an image? Does it crash if you only do text or only do an image?

What kind of image (PNG, JPG, etc) and roughly how big did you upload? Does it make a difference if you use a different kind of image? Or for that matter, does the problem only happen with one specific image? that case would be very interesting.

Comment 3

[akihiko.kigure]

Hi Daniel

After that, if you try the same thing, the crash window will suddenly appear.

If you mean have you sent the crash report to Apple then yes.

I don't know what that means

After saving a draft, the app becomes unresponsive.
Specifically, the cursor becomes a processing icon.

I couldn't do anything so I forced quit Firefox.
After that, if you try the same thing, the crash window will suddenly appear.

Do you have to both enter text AND upload an image? Does it crash if you only do text or only do an image?

1. This occurs when previewing an image after uploading it.
   　a. For images, only png, jpg
2. This occurs when you edit text, save it, and then preview it.

There are two patterns.

Comment 4

[:Gijs (he/him)]

Attachment: Firefox.crash.report..md

Gabriele, is there some way to symbolicate this apple crash report so we can triage this further?

(note also that the screenshots in the zipfile suggest that the crashreporter failed to load l10n information, which may be worth splitting off into its own bug...)

Comment 5

[Gabriele Svelto [:gsvelto]]

I should be able to symbolicate it using our addr2line machinery and the right symbols. I'll try today if I find some time. Not clearing the NI? for now so I don't forget.

CC'ing Alex for the localization issue.

Comment 6

[Gabriele Svelto [:gsvelto]]

I quickly looked up the address of the first frame and it matches this assertion.

Comment 7

[Gabriele Svelto [:gsvelto]]

This is likely an instance of bug 1880012.

Comment 8

[Alex Franchuk [:afranchuk]]

WRT the crashreporter client localization issue: the locale appears to be Japanese, however if possible I'd like to know the value of intl.locale.requested in about:config (if set at all), and to know how Firefox was installed (whether it was installed as the version bundled with Japanese localization or as another version with a Japanese langpack added).

Comment 9

[akihiko.kigure]

Hi Alex
What would you like to know?
And how should you check it?

Filtered by about:config, locale, and intl.locale.requested

Comment 10

[akihiko.kigure]

Attachment: about:config-1.png

Comment 11

[akihiko.kigure]

Attachment: about:config-2.png

Comment 12

[Alex Franchuk [:afranchuk]]

I think that gives me enough context. It appears that it's a Japanese-localized installation, since there is no alternative locale (and thus no langpack) configured.

Comment 13

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 14

[Stephen A Pohl [:spohl] (OOO until 1/26)]

(In reply to Gabriele Svelto [:gsvelto] from comment #6)

I quickly looked up the address of the first frame and it matches this assertion.

(In reply to Gabriele Svelto [:gsvelto] from comment #7)

This is likely an instance of bug 1880012.

Moving to DOM: Service Workers based on comment 6 and comment 7.