Firefox/Iceweasel Bug

Firefox/Iceweasel Bug

Bug: Firefox/iceweasel crashes when upload file dialog window pops open.

Here are ways to to replicate the bug:

  1. Try to attach a file with gmail.
  2. Try uploading folder/files with Google Drive
  3. Try to add hpkg file with github
  4. Pretty much any Add File dialog window ( with one exception see below )

I have run into this bug many times before and just dealt with it as best I know how.

One caveat or work-around to this bug that I have discovered is using github “Paste, Drop or Click to add Files” mouse click
screenshot1

  • Work-around:
  1. Select the “Paste, Drop or Click to add files”
  2. Select a folder in the Dialog window,
  3. Select another folder
  4. Repeat steps 2 and 3 several times
  5. Close the dialog window
  • Now, adding attachments to Gmail, adding folders/files with Google Drive, and hpkg files to github will not crash Firefox/iceweasel.

If I were to restart firefox/iceweasel, I have to repeat the work-around to stop the crash during the current Firefox/Iceweasel session.

Last but not least, in my normal Haiku nightly system, this bug eventually disappeared. I chalked it up to maybe one of the Devs had eventually fixed the bug. However, when I install Haiku6 I notice the bug had returned.

One thing I tried to see if it might be helpful

  • I installed every hpkg package that was on my stable Haiku system ( where Iceweasel eventually stopped crashing on its own ) thinking maybe it was related to a hpkg package on that system, to the Haiku6 system. But no avail - The crash is still happening.

Has any one else ran into this issue?

1 Like

Welp,

This issue has resolved itself again in Haiku6

I’m not sure but since I am using @X512 nebula driver, I thought I would see what would happen if I disabled it and reverted to the stock mesa/gl driver by doing this:

  • pkgman install mesa_devel glu_devel mesa_swpipe mesa_lavapipe glew_devel
    uninstall libglvnd-1.7.0-4-x86_64.hpkg

The above will revert Haiku to the stock GL/mesa stack even though nebula driver is loaded in memory.

From there I opened and tested Firefox and the crash bug did not happen.
So, I tried enabling nebula again by installing libglvnd-1.7.0-4-x86_64.hpkg first, then nebula-0.0.2-1.x86_64.hpkg, but the crash did not happened.

So, this is another one of those “I have no clue what is going on” :stuck_out_tongue:

Sorry, I’m not trying to be offensive but this has to be said.
The forum isn’t a bug tracker. Issues with 3rd parties apps must be reported where the app is originated. In this case, the app belongs to Haikuports repo, so it’s Haikuports bug tracker.
Here things are buried fast and with beta 6 release it will be even faster. And a report buried is a bug not fixed.

3 Likes

I’ve actually been having the same issue for a while now with Iceweasel and now Firefox. I’ve opened a ticket on the HaikuPorts GitHub about it as your post reminded me, just I hardly upload files so I forgot about doing it. It seems to not have anything to do with the Nebula driver as it happens to me with or without it installed.

The ticket I opened is here: Iceweasel and Firefox 153.0.3 crash with 'Illegal Instruction' error when trying to open a file open dialog to upload files. · Issue #14580 · haikuports/haikuports · GitHub

EDIT: Turns out there already was a ticket open from April 2025 that I didn’t see in my initial search so others have been having it for quite a while: Haiku latest nightly iceweasel exits when clicking the button to upload a syslog · Issue #12227 · haikuports/haikuports · GitHub

The way to fix it is in this forum thread: Firefox (all forks) randomly crashes on my laptop - #18 by 3dEyes

The following terminal commands need to be run to delete the files to fix the issue:

rm -rf /boot/system/non-packaged/data/mime

rm -rf /boot/home/config/non-packaged/data/mime

That did the trick for me and now the file open dialog works.

3 Likes

No offense taking.

Awesome! Appreciate ya!

This problem has nothing to do with Firefox. It’s a problem with the glib2 library.

At the moment, it is solved as described above - by deleting the mime directories in non-packaged.

4 Likes