Thanks for reporting this, Shiva! Just echoing some of what is listed in the GitHub bug, I also saw: ``` 07-02 11:50:33.791 2039 2912 I Gecko : IPDL protocol Error: Received an invalid file descriptor 07-02 11:50:33.795 2039 2295 E Web Content: [JavaScript Error: "Unexpected server response. 07-02 11:50:33.795 2039 2295 E Web Content: 07-02 11:50:33.795 2039 2295 E Web Content: PDF.js v4.5.7 (build: ccad2f889) 07-02 11:50:33.795 2039 2295 E Web Content: Message: Unexpected server response (0) while retrieving PDF "blob:https://mozilla.github.io/b14e6e40-45ff-4c07-a702-cd21866b3c10"."] 07-02 11:50:33.795 2039 2295 E Web Content: [JavaScript Error: "uncaught exception: Object"] 07-02 11:50:34.435 1857 1857 D GeckoSession: handleMessage GeckoView:StateUpdated uri=null 07-02 11:50:35.273 500 1312 E TaskPersister: File error accessing recents directory (directory doesn't exist?). ``` And it mysteriously works on the second attempt. I also see this in the logs as an error: ``` 07-02 11:53:38.072 3268 3268 E ViewConfiguration: Tried to access UI constants from a non-visual Context:com.android.documentsui.DocumentsApplication@5a3e008UI constants, such as display metrics or window metrics, must be accessed from Activity or other visual Context. Use an Activity or a Context created with Context#createWindowContext(int, Bundle), which are adjusted to the configuration and visual bounds of an area on screen 07-02 11:53:38.072 3268 3268 E ViewConfiguration: java.lang.IllegalArgumentException: Tried to access UI constants from a non-visual Context:com.android.documentsui.DocumentsApplication@5a3e008 ``` Just highlighting this is a regression, from the original report: >I tried with an older Fenix version and could not reproduce the issue. I then did a bisect with Fenix versions and found that the first bad version is 124.0b1. Blob support keeps coming up around PDFs as well, like in bug 1553790 and bug 1891737. Not sure if it is related, but it is something that keeps showing up. I think(?) [this](https://github.com/mozilla/pdf.js/blob/ccad2f889ae8e721b1a1119190f03f99c68ae763/web/app.js#L674) is the relevant PDF.js code that is called. So, it looks like an `input` to get the file and [here](https://github.com/mozilla/pdf.js/blob/ccad2f889ae8e721b1a1119190f03f99c68ae763/web/app.js#L2417) is where the blob is made. Calixte, does anything stand out to you?
Bug 1902898 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for reporting this, Shiva! Just echoing some of what is listed in the GitHub bug, I also saw: ``` 07-02 11:50:33.791 2039 2912 I Gecko : IPDL protocol Error: Received an invalid file descriptor 07-02 11:50:33.795 2039 2295 E Web Content: [JavaScript Error: "Unexpected server response. 07-02 11:50:33.795 2039 2295 E Web Content: 07-02 11:50:33.795 2039 2295 E Web Content: PDF.js v4.5.7 (build: ccad2f889) 07-02 11:50:33.795 2039 2295 E Web Content: Message: Unexpected server response (0) while retrieving PDF "blob:https://mozilla.github.io/b14e6e40-45ff-4c07-a702-cd21866b3c10"."] 07-02 11:50:33.795 2039 2295 E Web Content: [JavaScript Error: "uncaught exception: Object"] 07-02 11:50:34.435 1857 1857 D GeckoSession: handleMessage GeckoView:StateUpdated uri=null 07-02 11:50:35.273 500 1312 E TaskPersister: File error accessing recents directory (directory doesn't exist?). ``` And it mysteriously works on the second attempt. Probably where the `Received an invalid file descriptor` [message came from](https://searchfox.org/mozilla-central/rev/b368ed8b48c0ea8ed2f1948e4776a6fbb5976dff/ipc/glue/FileDescriptor.cpp#111). I also see this in the logs as an error: ``` 07-02 11:53:38.072 3268 3268 E ViewConfiguration: Tried to access UI constants from a non-visual Context:com.android.documentsui.DocumentsApplication@5a3e008UI constants, such as display metrics or window metrics, must be accessed from Activity or other visual Context. Use an Activity or a Context created with Context#createWindowContext(int, Bundle), which are adjusted to the configuration and visual bounds of an area on screen 07-02 11:53:38.072 3268 3268 E ViewConfiguration: java.lang.IllegalArgumentException: Tried to access UI constants from a non-visual Context:com.android.documentsui.DocumentsApplication@5a3e008 ``` Just highlighting this is a regression, from the original report: >I tried with an older Fenix version and could not reproduce the issue. I then did a bisect with Fenix versions and found that the first bad version is 124.0b1. Blob support keeps coming up around PDFs as well, like in bug 1553790 and bug 1891737. Not sure if it is related, but it is something that keeps showing up. I think(?) [this](https://github.com/mozilla/pdf.js/blob/ccad2f889ae8e721b1a1119190f03f99c68ae763/web/app.js#L674) is the relevant PDF.js code that is called. So, it looks like an `input` to get the file and [here](https://github.com/mozilla/pdf.js/blob/ccad2f889ae8e721b1a1119190f03f99c68ae763/web/app.js#L2417) is where the blob is made. Calixte, does anything stand out to you?