Open Bug 1497129 Opened 6 years ago Updated 2 years ago

[Linux] Segfaults while using HTML5 based image uploaders

Categories

(Firefox :: File Handling, defect, P5)

62 Branch
x86_64
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: vinibali1, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce:

Click on the image broswer icon or using the drag and drop function.


Actual results:

1 cpu core fully utilized with one process. Which got stuck and after a force kill, new lines appear in the kernel message and systemd-coredump runs.
Same problem with both firefox 62.0.1-1 and 62.0.3-1 while uploading photos to eBay's resolution center.



Expected results:

Successful image upload
[okt 8 09:23] Cameras IPC[4403]: segfault at 0 ip 00005644b6ebf5b1 sp 00007f42730e4870 error 6 in firefox[5644b6eba000+32000]
[  +0,000152] Cameras IPC[1389]: segfault at 0 ip 00005555a42775b1 sp 00007fbdc48fe870 error 6 in firefox[5555a4272000+32000]
[  +0,000176] Chrome_~dThread[1112]: segfault at 0 ip 00007f75e6d801f3 sp 00007f75e2c71b00 error 6 in libxul.so[7f75e6d77000+4b01000]
[okt 8 09:41] Chrome_~dThread[5633]: segfault at 0 ip 00007f3e31f87d73 sp 00007f3e2de79b00 error 6 in libxul.so[7f3e31f7f000+4b1a000]
[  +0,002602] Chrome_~dThread[5699]: segfault at 0 ip 00007ff3b8ba7d73 sp 00007ff3b4aa9b00 error 6 in libxul.so[7ff3b8b9f000+4b1a000]
[  +0,000173] Chrome_~dThread[5693]: segfault at 0 ip 00007f17e159fd73 sp 00007f17dd491b00 error 6
[  +0,000002] Chrome_~dThread[5709]: segfault at 0 ip 00007fa6cde17d73 sp 00007fa6c9d29b00 error 6 in libxul.so[7fa6cde0f000+4b1a000]
[  +0,000007]  in libxul.so[7f17e1597000+4b1a000]
Do you use Firefox from the package manager or the Firefox binaries from Mozilla website?
Would you have a test case to reproduce it?
Do you have a crash report in about:crashes? if so, could you please share it?
Flags: needinfo?(vinibali1)
I'm using the one from Arch Linux's repository and no crash report found/sent in the about:crashes.
Flags: needinfo?(vinibali1)
Did you report bug on the arch bug tracker also?
Flags: needinfo?(vinibali1)
Not yet, but I have an idea about the possible solution. I will update the ticket after the next stable kernel relese. 4.19 will come possibly in this weekend.

Thanks
Flags: needinfo?(vinibali1)
This might be a specific Linux-OS related issue as I'm not able to reproduce this on Ubuntu 18.10 x64 with 62.0.
Component: Untriaged → File Handling
Flags: needinfo?(vinibali1)
Per Comment 6, please update us if the issue is reproducible in Arch Linux 4.19.
Priority: -- → P5
Sorry for the late. The problem still exists, on my up2date system.
I though it could be because of xorg-server 1.20 is so new for the Linux 4.13, but the problem still exists while uploading bigger pictures to websites.
The confirmed lowest problematic picture size is about 7Mpx (1MB) up to 13MB (3-4MBs). These are the resolution which I used to upload. Uploading pictures up to 200-400KBs are fine.
Tell me if you need more exact numbers and the way how can I upload proper logs for analysis.

Best regards
Flags: needinfo?(vinibali1)
After installing the 63.0.3 version, this bug no longer affects me.

Regards
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.