body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScriptを使用できません。

このブラウザではJavaScriptが無効になっています。引き続きtwitter.comを利用するため、JavaScriptを有効にするか、サポートされているブラウザに切り替えてください。サポートされているブラウザのリストについては、ヘルプセンターをご覧ください。

ヘルプセンター

利用規約プライバシーポリシー Cookieのポリシー Imprint 広告情報 © 2023 Twitter, Inc.

アプリを使う

新しいツイートを表示

Twitterアプリをおすすめします

ツイートをお見逃しなく。Twitterアプリで開くとすべての機能を利用できます。

今はしない

アプリに切り替え

会話

2020年5月31日

So, this is happening with a Pixel 3 XL with Android 10, but not on a Pixel 4 XL with Android 11. Here's what's happening:

引用ツイート

Ice universe

@UniverseIce

2020年5月31日

WARNING！！！ Never set this picture as wallpaper, especially for Samsung mobile phone users! It will cause your phone to crash! Don't try it! If someone sends you this picture, please ignore it.

このスレッドを表示

11

244

293

2020年5月31日

The following image shows the stack trace of the crash of SystemUI. This basically means it's happening in "getHistogram".

3

16

62

2020年5月31日

After digging into getHistogram for both devices, and the functions calling getHistogram... I noticed this. The first image is from the Pixel 3 XL, while the second is from the Pixel 4 XL. On the Pixel 4 XL, there's a new parameter for the function peekWallpaperBitmap.

1

10

58

2020年5月31日

I won't show everything, but basically, the function doColorManagement of the ColorManagementProxy is called at some point. This function checks if the Color Space of the image is supported by the device. The image is supported by default if its color space is SRGB, or...

2

30

77

2020年5月31日

... if the current display supports it. If it isn't supported, it will replace the Color Space of the image to SRGB, and it will log its current Color Space. This is why it doesn't crash on the Pixel 4 XL. However, on the Pixel 3 XL with Android 10...

2

11

58

2020年5月31日

...this is not verified. This means that an image with a Color Space that isn't supported will likely cause a crash on that device if it is set as the wallpaper. So what's the Color Space of this image? RGB.

9

12

69

返信先:

さん

RGB is a color model, not a color space. Non-sRGB color spaces doesn't mean values outside of the 0..255 range. This is a separate thing as well. What is more likely a simply a rounding error either in the color space conversion or in the luma conversion done for the histogram

ツイートを翻訳

午後8:01 · 2020年6月3日

件のリツイート

件のいいね

1

ブックマーク

2020年6月3日

返信先:

さん,

さん

Does the explanation offered in this commit seem right to you as to the root cause of this bug? review.lineageos.org/c/LineageOS/an

1

1

4

2020年6月3日

返信先:

さん,

さん

Yes, that seems like the correct explanation. It would also be cheaper this way if the “grayscale” image is not needed elsewhere.

1

1

返信を表示

2020年6月3日

返信先:

さん

I – indeed – wrongly assumed that all color spaces wouldn't be supported. Thanks for the clarification.

1

Romeshwar Prasad

@RomeshwarPrasad

返信先:

さん,

さん

1

返信をさらに表示