Closed Bug 1607060 Opened 5 years ago Closed 1 year ago

[sway] [wayland] Bookmarks menu crashes

Categories

(Core :: Widget: Gtk, defect, P3)

71 Branch
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: qnf78597, Unassigned)

References

(Blocks 1 open bug)

Details

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

Steps to reproduce:

  1. Bookmarks > Show All Bookmarks.
  2. Select a single bookmark to open. (Doesn't occur if I open two or more.)
  3. Focus browser window.

or...

  1. Bookmarks > Show All Bookmarks.
  2. Focus newly opened bookmarks window.
  3. Go back to Firefox and click Bookmarks > Show All Bookmarks again.
  4. Focus bookmarks window again.

Actual results:

Immediate crash at the last step in both cases. Stack trace identical:

Stack trace of thread 123:
#0 0x00007fc87b0c84e1 n/a (libxul.so + 0x342f4e1)
#1 0x00007fc87b0c8c3d n/a (libxul.so + 0x342fc3d)
#2 0x00007fc87b0c8b5e n/a (libxul.so + 0x342fb5e)
#3 0x00007fc87b0c462a n/a (libxul.so + 0x342b62a)
#4 0x00007fc87b0c4413 n/a (libxul.so + 0x342b413)
#5 0x00007fc87b0c485a n/a (libxul.so + 0x342b85a)

Expected results:

It should have stopped raining outside.

Just kidding... guess it shouldn't crash. :)

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: wayland-sway
Priority: -- → P3

Can confirm it's still happening on Firefox version 76.0a1 (2020-03-10), Sway version 1.4, wlroots version 0.10.0.

While firefox crashes if you go through the All Bookmarks window, it doesn't crash if you access your bookmarks through the sidebar menu, shortcut CTRL+B. Since you can rearrange, edit, and create new bookmarks/folders doing it that way is a reasonable alternative at this point.

Is this issue still valid? Thanks

Flags: needinfo?(qnf78597)
Severity: normal → S3
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(qnf78597)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.