While working on removing support for `application/http-index-format` (Bug 1824325), I noticed the following bug. To reproduce: 1. Set up webserver which responds with a [valid directory listing](https://www-archive.mozilla.org/projects/netlib/dirindexformat), for example `100: You seem to have gotten the directory listing!` and with content type `application/http-index-format` (One such server is running at https://http-index-format.polar.onl via nginx 1.18.0-6ubuntu14.4) 2. Visit that server Expected result: We see a directory listing with the content "You seem to have gotten the directory listing!" Actual result: We get the error "Gah. Your tab just crashed." with not much more information This only seems to happen on real websites and not on pages like file:/// or resource:///, which use the same content type to display the directory listing. Additionally, every time the crash happens, I see `[Parent 45727, IPC I/O Parent] WARNING: process 46877 exited on signal 11: file /home/maltejur/mozilla-unified-3/ipc/chromium/src/base/process_util_posix.cc:265` in the terminal. As we probably want to remove web-facing support for that content type anyways, I am not sure if a direct fix is event required. I still wanted to report this issue though, because maybe it is a wider issue that is not just affecting `application/http-index-format`.
Bug 1871048 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
While working on removing support for `application/http-index-format` (Bug 1824325), I noticed the following bug. Regression testing suggests it is was introduced by Bug 1871048. To reproduce: 1. Set up webserver which responds with a [valid directory listing](https://www-archive.mozilla.org/projects/netlib/dirindexformat), for example `100: You seem to have gotten the directory listing!` and with content type `application/http-index-format` (One such server is running at https://http-index-format.polar.onl via nginx 1.18.0-6ubuntu14.4) 2. Visit that server Expected result: We see a directory listing with the content "You seem to have gotten the directory listing!" Actual result: We get the error "Gah. Your tab just crashed." with not much more information This only seems to happen on real websites and not on pages like file:/// or resource:///, which use the same content type to display the directory listing. Additionally, every time the crash happens, I see `[Parent 45727, IPC I/O Parent] WARNING: process 46877 exited on signal 11: file /home/maltejur/mozilla-unified-3/ipc/chromium/src/base/process_util_posix.cc:265` in the terminal. As we probably want to remove web-facing support for that content type anyways, I am not sure if a direct fix is event required. I still wanted to report this issue though, because maybe it is a wider issue that is not just affecting `application/http-index-format`.
While working on removing support for `application/http-index-format` (Bug 1824325), I noticed the following bug. Regression testing suggests it is was introduced by Bug 1871048. To reproduce: 1. Set up webserver which responds with a [valid directory listing](https://www-archive.mozilla.org/projects/netlib/dirindexformat), for example `100: You seem to have gotten the directory listing!` and with content type `application/http-index-format` (One such server is running at https://http-index-format.polar.onl via nginx 1.18.0-6ubuntu14.4) 2. Visit that server Expected result: We see a directory listing with the content "You seem to have gotten the directory listing!" Actual result: We get the error "Gah. Your tab just crashed." with not much more information This only seems to happen on real websites and not on pages like file:/// or resource:///, which use the same content type to display the directory listing. Additionally, every time the crash happens, I see `[Parent 45727, IPC I/O Parent] WARNING: process 46877 exited on signal 11: file /home/maltejur/mozilla-unified-3/ipc/chromium/src/base/process_util_posix.cc:265` in the terminal. As we probably want to remove web-facing support for that content type anyways, I am not sure if a direct fix is even required. I still wanted to report this issue though, because maybe it is a wider issue that is not just affecting `application/http-index-format`.
While working on removing support for `application/http-index-format` (Bug 1824325), I noticed the following bug. Regression testing suggests it is was introduced by Bug 1871048. To reproduce: 1. Set up webserver which responds with a [valid directory listing](https://www-archive.mozilla.org/projects/netlib/dirindexformat), for example `100: You seem to have gotten the directory listing!` and with content type `application/http-index-format` (One such server is running at https://http-index-format.polar.onl via nginx 1.18.0-6ubuntu14.4) 2. Visit that server Expected result: We see a directory listing with the content "You seem to have gotten the directory listing!" Actual result: We get the error "Gah. Your tab just crashed." with not much more information This only seems to happen on real websites and not on pages like file:/// or resource:///, which use the same content type to display the directory listing. Additionally, every time the crash happens, I see `[Parent 45727, IPC I/O Parent] WARNING: process 46877 exited on signal 11: file /home/maltejur/mozilla-unified-3/ipc/chromium/src/base/process_util_posix.cc:265` in the terminal. As we probably want to remove web-facing support for that content type anyways, I am not sure if a direct fix is even required. I still wanted to report this issue though, because maybe it is a wider problem that is not just affecting `application/http-index-format`.
While working on removing support for `application/http-index-format` (Bug 1824325), I noticed the following bug. Regression testing suggests it is was introduced by Bug 1871048. To reproduce: 1. Set up webserver which responds with a [valid directory listing](https://www-archive.mozilla.org/projects/netlib/dirindexformat), for example `100: You seem to have gotten the directory listing!` and with content type `application/http-index-format` (One such server is running at https://http-index-format.polar.onl via nginx 1.18.0-6ubuntu14.4) 2. Visit that server Expected result: We see a directory listing with the content "You seem to have gotten the directory listing!" Actual result: We get the error "Gah. Your tab just crashed." with not much more information This only seems to happen on real websites and not on pages like file:/// or resource:///, which use the same content type to display the directory listing. Additionally, every time the crash happens, I see `[Parent 45727, IPC I/O Parent] WARNING: process 46877 exited on signal 11: file /home/maltejur/mozilla-unified-3/ipc/chromium/src/base/process_util_posix.cc:265` in the terminal. This is the generated crash report https://crash-stats.mozilla.org/report/index/de3fc8a9-ba5c-42fa-a2dc-f2b020231220. As we probably want to remove web-facing support for that content type anyways, I am not sure if a direct fix is even required. I still wanted to report this issue though, because maybe it is a wider problem that is not just affecting `application/http-index-format`.
While working on removing support for `application/http-index-format` (Bug 1824325), I noticed the following bug. Regression testing suggests it was introduced by Bug 1871048. To reproduce: 1. Set up webserver which responds with a [valid directory listing](https://www-archive.mozilla.org/projects/netlib/dirindexformat), for example `100: You seem to have gotten the directory listing!` and with content type `application/http-index-format` (One such server is running at https://http-index-format.polar.onl via nginx 1.18.0-6ubuntu14.4) 2. Visit that server Expected result: We see a directory listing with the content "You seem to have gotten the directory listing!" Actual result: We get the error "Gah. Your tab just crashed." with not much more information This only seems to happen on real websites and not on pages like file:/// or resource:///, which use the same content type to display the directory listing. Additionally, every time the crash happens, I see `[Parent 45727, IPC I/O Parent] WARNING: process 46877 exited on signal 11: file /home/maltejur/mozilla-unified-3/ipc/chromium/src/base/process_util_posix.cc:265` in the terminal. This is the generated crash report https://crash-stats.mozilla.org/report/index/de3fc8a9-ba5c-42fa-a2dc-f2b020231220. As we probably want to remove web-facing support for that content type anyways, I am not sure if a direct fix is even required. I still wanted to report this issue though, because maybe it is a wider problem that is not just affecting `application/http-index-format`.