Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,680,249 | 15,155,595 |
Created attachment 9190797
screenshots-weibo.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
1)Install firefox 83.0 stable or firefox nightly
2)open weibo.com
Hi,
Today, i found i can not access some websites, and Firefox didn't provide any specific error message like error code etc...(both firefox developer tools and error page itself).
Please help me troubleshoot this problem, thanks. Screenshots are attached below.
PS:
1.Using windows defender only(and without any intercept log)
2.Not work on new profile either
3.Other browsers work without any problem.
4.Firefox nightly still have this problem.
5.Tried with another computer with fresh windows&firefox installation, but still not work.
Actual results:
The page navigate to passport.weibo.com and then firefox show a error page without any additional information about what really happened.
Expected results:
This website should load successfully without any problem.
|
|
1,680,313 | 15,156,025 |
The change in bug 1665329 appears to cause resolution problems with some WebRTC calls. Let's revert the pref until we can find the bug in the Media Data Decoder.
|
|
1,680,589 | 15,158,111 |
1. Enable VO
2. Navigate to `data:text/html,<button>Before</button><div role="tree" tabindex="0" aria-label="My drive" aria-activedescendant="myfiles"><div id="myfiles" role="treeitem" aria-label="My files" aria-selected="true" aria-expanded="false">My files</div><div role="treeitem" aria-label="Shared items" aria-selected="false" aria-expanded="false">Shared items</div></div>`
3. VO+next past the button, VO+Shift+Down to enter the tree, focus on the first row
Expected:
VO says the first row is collapsed
Actual:
VO says nothing about expanded/collapsed status
|
|
1,680,791 | 15,159,561 |
Created attachment 9191353
blank newtab.mp4
**[Affected versions]:**
- Firefox Beta 84.0b8 (Build ID: 20201203211213)
**[Affected Platforms]:**
- Windows 10
- macOS 10.15
- Linux Mint 20
**[Prerequisites]:**
- Have Firefox installed.
- Have [this user.js](https://drive.google.com/file/d/1tJpzHjPbXq6VuUmEjhYsscAkkuYewk2E/view?usp=sharing) file saved (made for web+normandy://stage/recipes/1325, used for testing [PI-873](https://jira.mozilla.com/browse/PI-873)).
**[Steps to reproduce]:**
1. Create a new profile.
2. Go to “about:support” and open the Profile Directory folder.
3. Copy paste the user.js file from prerequisites.
4. Make sure you have no “about:newtab” page open and restart the browser.
5. Open a new tab.
**[Expected result]:**
- The “about:newtab” page is populated with content.
**[Actual result]:**
- The “about:newtab” page is completely blank.
**[Notes]:**
- The issue is also reproducible using a VPN set to the US and removing the region specific preferences from user.js.
- about:newtab pages already open before the restart will contain content.
- The issue is also reproducible for the Control branch.
- This issue is not reproducible if the user restarts the browser once after the region is set and then enrols in the experiment.
- Attached is a [recording](https://drive.google.com/file/d/1JziNpLXi96nWRSi8njU-9T-Jz1juGOJF/view?usp=sharing) of the issue.
|
|
1,680,843 | 15,160,025 |
Created attachment 9191420
Testcase 1: sMimeSenderHeaderTest.eml with `From` != `signer address`
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
Starting with Thunderbird 78, running Windows 10 or Linux x64, we observe the erroneous displaying of a "Sender:" header if a particular type of message was previewed. The "Sender:" header of the triggering message is then display on all subsequently viewed messages.
Steps to reproduce:
Thunderbird 78.x, tested up to 78.5.1;
add the attached minimal example S/MIME signed message `smimesendertest.eml` to a folder (IMAP or local);
preview the message (or open it in a tab).
Actual results:
The example message includes the header `Sender: FALSE SENDER <[email protected]>` which is correctly displayed in the preview. After this, the same header will be shown on all subsequently previewed messages (or ones open in tabs) which is of course incorrect.
Testing showed that a crucial condition of messages that trigger this bug is the fact that the RFC5322-From of the S/MIME signed message does not match the signers address. We observed this on a local mailing list that changes the "From:".
|
|
1,681,072 | 15,163,455 |
[Tracking Requested - why for this release]: Hang that can cause the browser to be unresponsive as a whole. Should be fixed for Firefox 85, either directly or as an uplift from 86 during the 85 beta cycle.
Steps:
1. Turn on VoiceOver and open a tab to the Mozilla Slack workspace.
2. Tab to the Help menu, choose Keyboard Shortcuts.
3. Start navigating in the side bar of keyboard shortcuts.
Result: Either immediately, or after a short while, Firefox starts to freeze and spin up the CPU fan like crazy. VoiceOver goes "Firefox busy"...
From now on, if the tab is reopened with the keyboard shortcut listing open in the side bar, the tab will freeze the whole browser immediately if VoiceOver is active.
|
|
1,682,242 | 15,173,478 |
With the patch on bug 1676671 landed, the initial browser collection is broken if there is a non-browser window open. The failure looks like:
```
1607940033466 Marionette DEBUG 3 <- [1,1,{"error":"unknown error","message":"TypeError: can't access property \"tabs\", tabBrowser is null","stacktrace":"GeckoDr ... t@chrome://marionette/content/server.js:241:9\n_onJSONObjectReady/<@chrome://marionette/content/transport.js:504:20\n"},null]
Marionette threw an error: TypeError: can't access property "tabs", tabBrowser is null
GeckoDriver.prototype.newSession@chrome://marionette/content/driver.js:876:25
despatch@chrome://marionette/content/server.js:297:40
execute@chrome://marionette/content/server.js:267:16
onPacket/<@chrome://marionette/content/server.js:240:20
onPacket@chrome://marionette/content/server.js:241:9
_onJSONObjectReady/<@chrome://marionette/content/transport.js:504:20
```
|
|
1,682,692 | 15,177,611 |
STR:
1. Open a slack instance in Firefox
2. Press ctrl+/ to open keyboard shortcuts pane.
3. Go to list item containing string "Move focus through messages"
Result:
List item is named "Move focus through messages up arrow key down arrow key or"
Expected:
List item should be named "Move focus through messages up arrow or key down arrow key"
Looks like slack is doing a bunch of tree stylings and mutations that mess with our insertion processing code. The insertions queue for the listitem container contains both redundant nodes, and unparented nodes. Some combination of this is causing us to reinsert children in the wrong order.
|
|
1,682,713 | 15,177,700 |
M1 Mac Mini / macOS 11.1 / Firefox Beta 85b1
When the Mac wakes up from sleep, Firefox is unresponsive: windows do not accept input.
Interestingly, menu items work. I can open About Firefox for example.
STR is simple: run Firefox Beta 85b1. Select Sleep from the Apple menu. Wake up the machine.
|
|
1,683,299 | 15,182,330 |
+++ This bug was initially created as a clone of Bug #1649503 +++
Creating a new bug for this.
bug 1649503 comment 24
>It looks like this bug isn't really fixed at least as of 84.0b7. I've run into this issue and trying to look at the most recent looked at project in Gitlab for example only shows "This feature requires browser localStorage support".
bug 1649503 comment 26
>Same here, now that Firefox 84 has been released it broke our application that relies on storing ~ 1.6 MB of data in local storage. I managed to make the issue reproducible on a new profile using Firefox 84.0 using the following script running on a localhost server:
[...] read the linked comment
|
|
1,683,525 | 15,183,773 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Visit https://www.hetzner.com in Firefox Nightly 86.0a1 (2020-12-18) (64-bit) on macOS 10.15.7
Actual results:
I get an error that the certificate was revoked:
Secure Connection Failed
An error occurred during a connection to www.hetzner.com. Peer’s Certificate has been revoked.
Error code: SEC_ERROR_REVOKED_CERTIFICATE
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
The connection is fine in Chrome (stable) on the same laptop. Someone else in #nightly also confirms that they see the same error, so it's not just my connection, and that it's fine in Firefox release channel.
Expected results:
The site should work, I think.
Also, maybe it should get me some details on what the cert is? I don't see any option for it to tell me what it saw or why it decided it was revoked.
|
|
1,683,678 | 15,185,986 |
Created attachment 9194218
about_login_button.gif
*Affected versions*
* 86.0a1(20201221093813)
* 85.0b4 (20201220193140)
*Affected platforms*
* Windows 10x64
* macOS 10.15
* Ubuntu 18.04
*Preconditions*
* have a saved login and Light OS theme
*Steps to reproduce*
1. Open about:logins and select a random login.
2. Click on the Mask/ Unmask password button.
*Expected result*
* Buttons are displayed as expected.
*Actual result*
* Mask password button is invisible but can be activated.
*Regression range*
* Last good revision: 3652d2a382005d6c6755405734168ddeca937ff4
* First bad revision: cc1e3921893e658963369bdae4ab264f56474d5e
* Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3652d2a382005d6c6755405734168ddeca937ff4&tochange=cc1e3921893e658963369bdae4ab264f56474d5e
*Notes*
* Attached a screen recording.
**Suggested Severity: S3**
|
|
1,677,933 | 15,137,057 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
Open a PDF on a device with a touchscreen and use the two-finger zoom gesture(pinch-to-zoom).
Actual results:
Nothing
Expected results:
The pdf should zoom in and out, like if you did the same gesture on a touchpad
|
|
1,677,934 | 15,137,059 |
Crash report: https://crash-stats.mozilla.org/report/index/b4b3afe7-09b9-40df-94ed-c091b0201118
Reason: ```EXC_BAD_ACCESS / KERN_INVALID_ADDRESS```
Top 10 frames of crashing thread:
```
0 XUL -[MOXTextMarkerDelegate moxUIElementForTextMarker:] accessible/mac/MOXTextMarkerDelegate.mm:290
1 XUL -[MOXAccessibleBase accessibilityAttributeValue:forParameter:] accessible/mac/MOXAccessibleBase.mm:357
2 AppKit ___NSAccessibilityEntryPointValueForAttributeWithParameter_block_invoke.840
3 AppKit NSAccessibilityPerformEntryPointObject
4 AppKit NSAccessibilityEntryPointValueForAttributeWithParameter
5 AppKit CopyParameterizedAttributeValue
6 HIServices _AXXMIGCopyParameterizedAttributeValue
7 HIServices _XCopyParameterizedAttributeValue
8 HIServices mshMIGPerform
9 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__
```
I was reproducing a user reported perf issue on Mac and was interacting with the resulting page. I had VoiceOver on and a Braille display connected.
Steps:
1. Opened [this text file](https://t.co/stBtixTHjR?amp=1) in TextEdit and copied the whole string to the clipboard.
2. Went to [the screen reader version of Trimps](https://t.co/4ROt7XTeXd?amp=1).
3. Navigated to "Import", pasted the contents into the text field, and hit "Import" button.
4. Navigated the result. Interacted, navigated, stopped interacting. I believe the crash happened when I once went out of, and then back into, the web content itself.
|
|
1,678,734 | 15,142,169 |
Crash report: https://crash-stats.mozilla.org/report/index/731a6bb9-daa5-40da-b214-243250201113
MOZ_CRASH Reason: ```MOZ_RELEASE_ASSERT(traceable)```
This means that the channel parameter passed to `extensions::StreamFilterParent::Attach(channel, endpoints)` is NOT a `nsITraceableChannel`.
This is responsible for about half of the crashes attributed to that method in the past week, 45% in the past month, 44% in the past 3 months, 35% in the past 6 months, the others are in bug 1673749 (Aggregate on "Moz crash reason" to see them).
Of [the 495 crashes from the last 6 months related to this bug report](https://crash-stats.mozilla.org/signature/?product=Firefox&moz_crash_reason=%3DMOZ_RELEASE_ASSERT%28traceable%29&signature=mozilla%3A%3Aextensions%3A%3AStreamFilterParent%3A%3AInit&date=%3E%3D2020-08-20T21%3A25%3A00.000Z&date=%3C2020-11-20T21%3A25%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=-date&page=1#reports), "remote type" 52% are web, 41% are extension process crashes ("remote type").
18 users left comments, 8 claim that they were using View Source (Ctrl-U) before the crash.
Top 10 frames of crashing thread:
```
0 xul.dll mozilla::extensions::StreamFilterParent::Init toolkit/components/extensions/webrequest/StreamFilterParent.cpp:160
1 xul.dll static mozilla::extensions::StreamFilterParent::Attach toolkit/components/extensions/webrequest/StreamFilterParent.cpp:146
2 xul.dll std::_Func_impl_no_alloc<`lambda at /builds/worker/checkouts/gecko/docshell/base/nsDocShell.cpp:12374:20', nsresult, nsDocShellLoadState*, nsTArray<mozilla::ipc::Endpoint<mozilla::extensions::PStreamFilterParent> >&&, nsDOMNavigationTiming*>::_Do_call
3 xul.dll mozilla::dom::ChildProcessChannelListener::OnChannelReady docshell/base/ChildProcessChannelListener.cpp:33
4 xul.dll mozilla::dom::ContentChild::RecvCrossProcessRedirect dom/ipc/ContentChild.cpp:3490
5 xul.dll mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:12721
6 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2074
7 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1953
8 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:512
9 xul.dll mozilla::detail::RunnableFunction<`lambda at /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:83:7'>::Run xpcom/threads/nsThreadUtils.h:577
```
Searchfox links for top of stack: **note there is more than one trigger, see below**
0. `StreamFilterParent::Init` @ [toolkit/components/extensions/webrequest/StreamFilterParent.cpp#160](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/toolkit/components/extensions/webrequest/StreamFilterParent.cpp#160)
1. `StreamFilterParent::Attach` @ [toolkit/components/extensions/webrequest/StreamFilterParent.cpp#146](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/toolkit/components/extensions/webrequest/StreamFilterParent.cpp#146)
2. lambda for `ChildProcessChannelListener::RegisterCallback` in `nsDocShell::ResumeRedirectedLoad` @ [docshell/base/nsDocShell.cpp#12865-12866](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/docshell/base/nsDocShell.cpp#12865-12866)
* To save you from loading a file with 10k+ lines, the `channel` parameter is `aLoadState->GetPendingRedirectedChannel()` - [`nsDocShellLoadState::GetPendingRedirectedChannel`](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/docshell/base/nsDocShellLoadState.h#246)
* **NOTE: This is not the only responsible caller**. E.g. in bp-f30652dc-c1cc-4d82-9155-42d4f0201120 `Attach` was called by `DocumentChannelChild::OnRedirectVerifyCallback` @ [netwerk/ipc/DocumentChannelChild.cpp#370](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/netwerk/ipc/DocumentChannelChild.cpp#370)
3. `ChildProcessChannelListener::OnChannelReady` @ [docshell/base/ChildProcessChannelListener.cpp#33-34](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/docshell/base/ChildProcessChannelListener.cpp#33-34).
4. `ContentChild::RecvCrossProcessRedirect` @ [dom/ipc/ContentChild.cpp#3509](https://searchfox.org/mozilla-central/rev/2efcda6dc74c63863fd8f04a6d9d7ac6b09c7eca/dom/ipc/ContentChild.cpp#3509)
|
|
1,543,990 | 14,050,860 |
Created attachment 9057867
fx65-fx66-preconnect.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Open https://jg-testpage.github.io/wpt/preconnect.html in Firefox 66
It contains <link rel="preconnect"> + setTimeout(1000) HTTP request
Actual results:
<link rel="preconnect"> was ignored, and DNS+TCP+TLS happened at the HTTP request time
From my tests with devtools it seems it was working until Firefox 65 (see attachment)
Expected results:
DNS+TCP+TLS should have happened earlier
Firefox 66 KO https://www.webpagetest.org/result/190411_12_ed5cfb727a48dcea11b1a4f54999922c/1/details/
Firefox 68 Nightly KO https://www.webpagetest.org/result/190411_T3_3cb066d3ceb1fbd2be1bf33cfb491bf5/1/details/
Chrome OK https://www.webpagetest.org/result/190412_AQ_147b2535813e4324497d471e22d67445/1/details/
|
|
1,544,127 | 14,051,857 |
This bug is for crash report bp-02ca13fa-8b0a-4fca-956a-1e6660190410.
```
Top 10 frames of crashing thread:
0 xul.dll unsigned long mozilla::net::CookieSettings::Release netwerk/cookie/CookieSettings.cpp:246
1 xul.dll mozilla::net::LoadInfo::~LoadInfo netwerk/base/LoadInfo.h:139
2 xul.dll mozilla::net::LoadInfo::Release netwerk/base/LoadInfo.cpp:616
3 xul.dll mozilla::net::HttpBaseChannel::~HttpBaseChannel netwerk/protocol/http/HttpBaseChannel.cpp:254
4 xul.dll void mozilla::net::nsHttpChannel::~nsHttpChannel netwerk/protocol/http/nsHttpChannel.cpp:350
5 xul.dll unsigned long mozilla::dom::ExternalHelperAppParent::Release xpcom/base/nsSystemInfo.cpp:1050
6 xul.dll mozilla::dom::DeferredFinalizerImpl<nsISupports>::DeferredFinalize dom/bindings/BindingUtils.h:2695
7 xul.dll mozilla::IncrementalFinalizeRunnable::ReleaseNow xpcom/base/CycleCollectedJSRuntime.cpp:1253
8 xul.dll nsresult mozilla::IncrementalFinalizeRunnable::Run xpcom/base/CycleCollectedJSRuntime.cpp:1289
9 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1179
```
this crash signature is starting to show up in low volume in pre-release versions of firefox 67. the top frames of the stacks point to code recently touched in bug 1525245, so i assume that could be the regressor.
|
|
1,553,878 | 14,135,717 |
This bug is for crash report bp-14276951-5cf8-41a1-b550-0fd170190523.
```
Top 2 frames of crashing thread:
0 libxul.so void mozilla::jni::NativeStub<mozilla::java::GeckoSystemStateListener::OnDeviceChanged_t, mozilla::GeckoSystemStateListener, mozilla::jni::Args<> >::Wrap<&mozilla::GeckoSystemStateListener::OnDeviceChanged> widget/android/jni/Natives.h:710
1 base.odex base.odex@0x647b60
```
This is an assertion failure due to GeckoSystemStateListener.nativeOnDeviceChanged() being called from a non-UI thread. We should probably just remove that restriction from the @WrapForJNI annotation.
|
|
1,552,099 | 14,121,301 |
[Tracking Requested - why for this release]:
This bug is for crash report bp-14f8a344-f0c7-42b9-9a5a-f51fd0190516.
```
Top 10 frames of crashing thread:
0 xul.dll static bool EnqueuePromiseReactionJob js/src/builtin/Promise.cpp:1069
1 xul.dll static bool ResolvePromise js/src/builtin/Promise.cpp:1125
2 xul.dll static bool FulfillMaybeWrappedPromise js/src/builtin/Promise.cpp:1162
3 xul.dll static bool ResolvePromiseInternal js/src/builtin/Promise.cpp:862
4 xul.dll static bool ResolveOrRejectPromise js/src/jsapi.cpp:4038
5 xul.dll mozilla::dom::Promise::MaybeResolve dom/promise/Promise.cpp:298
6 xul.dll static void mozilla::dom::Promise::MaybeSomething<RefPtr<mozilla::dom::cache::Cache>&> dom/promise/Promise.h:251
7 xul.dll mozilla::dom::cache::CacheOpChild::Recv__delete__ dom/cache/CacheOpChild.cpp:158
8 xul.dll mozilla::dom::cache::PCacheOpChild::OnMessageReceived ipc/ipdl/PCacheOpChild.cpp:106
9 xul.dll void mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2087
```
this content crash signature is spiking up since 24 hours ago from users of zh-cn builds, so far there are about 700 submitted reports:
https://crash-stats.mozilla.com/signature/?useragent_locale=zh-cn&signature=EnqueuePromiseReactionJob&date=%3E%3D2019-05-01#graphs
urls in reports commonly show sites on the https://blog.csdn.net domain, so probably some change on the site there or from embedded ad scripts is starting to trigger this now
|
|
1,135,434 | 9,944,299 |
Created attachment 8567601
On IMAP, deleting attachment and moved.eml
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150122214805
Steps to reproduce:
While viewing a message in an IMAP folder (with "mark it as deleted" selected, in account settings), delete an attachment, using bottom-right pull-down item.
Move the original message to another (local) folder, or even just "View - Message Source".
Actual results:
The original message now contains the following messages from the original folder, as seen with "View - Message Source". After moving the original message to another folder, its message size now reflects the inclusion of those (many) following messages, with those messages now marked ">From" at their start,. But still, those extra messages don't appear when viewed normally. The IMAP system retains the correct original message; so a "repair folder" reloads the original message intact.
Expected results:
The original message should have remained unchanged locally.
|
|
1,415,923 | 12,831,417 |
MacOS X 10.12.6 (16G1036) - MacBookPro
Firefox becomes unresponsive / laggy after the screen was locked for some time. The UI responds with a multiple second delay until the browser is restarted. At first I though this was somehow related to my specific device. But now after switching to a new device I have the same problem again.
STR:
* Lock the screen - I usually execute "Lock" via the Alfred3 prompt). Note that it's "Lock" and not "Sleep".
* Wait some time - Usually I notice the behavior after longer breaks. It needs to be at least long enough so that macOS askes for the password again.
Not sure if it's important, but some details about my setup:
* Two external displays
* Two Firefox windows - One on an external screen and another one on the MacBook
* Some pages that are always open: GMail, Google Calendar, IRCCloud, Slack, Hangouts, GitHub, Bugzilla
|
|
1,793,392 | 16,096,661 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
Solaris build fails with:
```
28:17.24 Undefined first referenced
28:17.24 symbol in file
28:17.24 uprofiler_register_thread ../../../media/libcubeb/src/cubeb_oss.o (symbol scope specifies local binding)
28:17.24 uprofiler_unregister_thread ../../../media/libcubeb/src/cubeb_oss.o (symbol scope specifies local binding)
28:17.24 ld: fatal: symbol referencing errors
28:22.56 collect2: error: ld returned 1 exit status
28:22.57 gmake[4]: *** [/builds/psumbera/mozilla-central-build/config/rules.mk:540: libxul.so] Error 1
```
The first bad revision is:
changeset: 636755:7b25c38cf13b
user: Paul Adenot <[email protected]>
date: Sat Oct 01 00:59:45 2022 -0700
description:
Bug 1791900 - Update libcubeb 93d1fa3fcc. r=cubeb-reviewers,kinetik
Differential Revision: https://phabricator.services.mozilla.com/D157987
|
|
1,793,419 | 16,096,811 |
Created attachment 9296973
Screen Recording 2022-10-03 at 14.30.53.mov
**Found in**
- Firefox 106.0b7
**Affected versions**
- Firefox 106.0b7;
- Nightly 107.0a1;
**Tested platforms**
- macOS 12;
- Windows 10;
- Ubuntu 22;
**Affected platforms**
- macOS 12;
- Windows 10;
- Ubuntu 22;
**Steps to reproduce**
1. Launch Firefox and go to any pdf form, for example https://www.africau.edu/images/default/sample.pdf.
2. Click on the Text button from the upper right side of the PDF Toolbar.
3. Select a place on the PDF and enter any text.
4. Enable the screenreader(VoiceOver on macOS, NVDA on Windows, ORCA on Linux).
5. Focus the previously written text.
**Expected result**
- Screenreader should be able to read the text correctly.
**Actual result**
- Screenreader reads any text as "group"/"blank"(depending on OS).
**Regression range**
- Not a regressions since this is a new feature.
**Additional notes**
- I noticed that if the user is writing the text slowly with VoiceOver enabled, VoiceOver will read the input letter by letter. On Windows, NVDA reads "blank" instead of "group". Orca does not recognize the text at all on Linux if focused. Please see attached video with the issue.
|
|
1,793,521 | 16,097,775 |
Created attachment 9297059
testcase.html
Found while fuzzing m-c 20220924-50f72898d7b8 (--enable-debug --enable-fuzzing)
To reproduce via Grizzly Replay:
```
$ pip install fuzzfetch grizzly-framework
$ python -m fuzzfetch -d --fuzzing -n firefox
$ python -m grizzly.replay ./firefox/firefox testcase.html
```
Assertion failure: aRHEntry, at /builds/worker/checkouts/gecko/ipc/glue/BackgroundUtils.cpp:370
```
#0 0x7feb048ca8cc in mozilla::ipc::RHEntryToRHEntryInfo(nsIRedirectHistoryEntry*, mozilla::net::RedirectHistoryEntryInfo*) /builds/worker/checkouts/gecko/ipc/glue/BackgroundUtils.cpp:370:3
#1 0x7feb048cafd8 in mozilla::ipc::LoadInfoToLoadInfoArgs(nsILoadInfo*, mozilla::Maybe<mozilla::net::LoadInfoArgs>*) /builds/worker/checkouts/gecko/ipc/glue/BackgroundUtils.cpp:431:10
#2 0x7feb04452514 in mozilla::net::HttpBaseChannel::MaybeReportTimingData() /builds/worker/checkouts/gecko/netwerk/protocol/http/HttpBaseChannel.cpp:5320:5
#3 0x7feb044605e3 in mozilla::net::HttpChannelChild::DoPreOnStopRequest(nsresult) /builds/worker/checkouts/gecko/netwerk/protocol/http/HttpChannelChild.cpp:961:3
#4 0x7feb04460271 in mozilla::net::HttpChannelChild::OnStopRequest(nsresult const&, mozilla::net::ResourceTimingStructArgs const&, mozilla::net::nsHttpHeaderArray const&) /builds/worker/checkouts/gecko/netwerk/protocol/http/HttpChannelChild.cpp:906:3
#5 0x7feb044c783d in operator() /builds/worker/checkouts/gecko/netwerk/protocol/http/HttpChannelChild.cpp:795:15
#6 0x7feb044c783d in std::_Function_handler<void (), mozilla::net::HttpChannelChild::ProcessOnStopRequest(nsresult const&, mozilla::net::ResourceTimingStructArgs const&, mozilla::net::nsHttpHeaderArray const&, nsTArray<mozilla::net::ConsoleReportCollected>&&, bool)::$_22>::_M_invoke(std::_Any_data const&) /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/lib/gcc/x86_64-linux-gnu/7.5.0/../../../../include/c++/7.5.0/bits/std_function.h:316:2
#7 0x7feb04696c3b in mozilla::net::ChannelEventQueue::FlushQueue() /builds/worker/checkouts/gecko/netwerk/ipc/ChannelEventQueue.cpp:94:12
#8 0x7feb046ccd90 in mozilla::net::ChannelEventQueue::ResumeInternal()::CompleteResumeRunnable::Run() /builds/worker/checkouts/gecko/netwerk/ipc/ChannelEventQueue.cpp:152:17
#9 0x7feb03d51c8e in mozilla::RunnableTask::Run() /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:538:16
#10 0x7feb03d2a1a9 in mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:851:26
#11 0x7feb03d28d33 in mozilla::TaskController::ExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:683:15
#12 0x7feb03d28fa3 in mozilla::TaskController::ProcessPendingMTTask(bool) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:461:36
#13 0x7feb03d555a9 in operator() /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:190:37
#14 0x7feb03d555a9 in mozilla::detail::RunnableFunction<mozilla::TaskController::InitializeInternal()::$_1>::Run() /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:531:5
#15 0x7feb03d3edff in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1205:16
#16 0x7feb03d4540d in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:465:10
#17 0x7feb04926dc4 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:107:5
#18 0x7feb0484c477 in MessageLoop::RunInternal() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:381:10
#19 0x7feb0484c382 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:374:3
#20 0x7feb0484c382 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:356:3
#21 0x7feb08d0f568 in nsBaseAppShell::Run() /builds/worker/checkouts/gecko/widget/nsBaseAppShell.cpp:150:27
#22 0x7feb0af0991b in XRE_RunAppShell() /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:880:20
#23 0x7feb04927d0a in mozilla::ipc::MessagePumpForChildProcess::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:235:9
#24 0x7feb0484c477 in MessageLoop::RunInternal() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:381:10
#25 0x7feb0484c382 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:374:3
#26 0x7feb0484c382 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:356:3
#27 0x7feb0af08e33 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:739:34
#28 0x55ebf9897b39 in content_process_main /builds/worker/checkouts/gecko/browser/app/../../ipc/contentproc/plugin-container.cpp:57:28
#29 0x55ebf9897b39 in main /builds/worker/checkouts/gecko/browser/app/nsBrowserApp.cpp:359:18
#30 0x7feb1aa7b082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#31 0x55ebf986d8dc in _start (/home/worker/builds/m-c-20220924093346-fuzzing-debug/firefox-bin+0x168dc) (BuildId: 2943c95c5a50fc1ed463c4675ae883449afd8019)
```
|
|
1,793,800 | 16,099,949 |
Created attachment 9297277
CFR_Control.gif
**[Affected versions]:**
- Firefox Beta 106.0b7 - Build ID: 20221002185807
**[Affected Platforms]:**
- Windows 10 x64
- Windows 7 x64
- Windows 11 x64
- macOS 12.5.1
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have the Firefox Beta 106.0b7 browser installed.
- Have the channel pref set to “release”.
- Have this [user.js](https://drive.google.com/file/d/1ewFYwqu0BV3GfTPGsrHzVpOMri60a8F-/view?usp=sharing) saved on your computer.
- Have a new Firefox profile created.
- Have the Profile Folder opened.
**[Steps to reproduce]:**
1. Copy and paste the user.js file from prerequisites on the Profile Folder.
2. Open the Firefox profile from prerequisites.
3. Ensure that the profile is enrolled in the control branch of the experiment.
4. Close the browser.
5. Open the times.json file from Profile Folder and change the “created” and “firstUse” to “1664787790000” (timestamp for 3 October).
6. Open the browser using the same profile.
7. Open 4 new tabs and close 3 of them.
8. Click outside of the Adress Bar to switch focus.
9. Observe what happens.
**[Expected result]:**
- The Firefox View CFR message is not displayed.
**[Actual result]:**
- The Firefox View CFR message is shown.
**[Notes]:**
- This issue is reproducible in both existing and new experiments.
- Attached is a screen recording of the issue.
|
|
1,793,868 | 16,100,409 |
Created attachment 9297362
An admittedly sloppy test case
Firefox refuses to construct a WebSocket from WebAssembly. Specifically, `Reflect.construct.bind(null, WebSocket, ["ws://localhost:8080"])` is passed as an import when instantiating a WebAssembly module.
The module immediately calls the import from the start function.
This problem can be reproduced in the latest version of Firefox Nightly (build ID 20221005094233).
### Steps to reproduce
1. Download and extract the attached .zip file to some directory.
2. Open a terminal (like PowerShell).
3. Run `cd <path to files>` to enter that directory.
4. Run `npx serve .` (this assumes npm is installed on your system).
5. Open Firefox.
6. Navigate to http://localhost:3000.
### Expected result
The browser attempts to establish a WebSocket connection, and no error is displayed on the test page.
### Actual result
The browser refuses to attempt establishing a WebSocket connection and throws a SecurityError DOMException, which is displayed on the test page.
|
|
1,793,890 | 16,100,546 |
The [`enableNimbus(...)` helper](https://searchfox.org/mozilla-central/rev/d0f5bc50aff3462c9d1546b88d60c5cb020eb15c/toolkit/components/backgroundtasks/BackgroundTasksUtils.jsm#300) invokes [`lazy.RemoteSettingsExperimentLoader.init()`](https://searchfox.org/mozilla-central/rev/d0f5bc50aff3462c9d1546b88d60c5cb020eb15c/toolkit/components/nimbus/lib/RemoteSettingsExperimentLoader.jsm#132), which in turn will trigger Remote Settings sync if
* there is no local DB AND no local dump saved; or
* while verifying the signature, the metadata comes up empty
Background Tasks are short lived and don't schedule Remote Settings timers. That means that after the first run, the Remote Settings data will not be updated and will potentially be stale. (I have witnessed this locally by looking at saved timestamps.)
This ticket tracks forcing a Remote Settings sync of the Nimbus recipes collection when in background task mode.
|
|
1,794,061 | 16,101,641 |
Crash report: https://crash-stats.mozilla.org/report/index/10c8bbcc-bcb9-4444-9f3f-289540221006
Reason: ```EXC_BAD_ACCESS / KERN_INVALID_ADDRESS```
Top 10 frames of crashing thread:
```
0 XUL nsCOMPtr_base::assign_assuming_AddRef xpcom/base/nsCOMPtr.h:372
0 XUL nsCOMPtr_base::assign_with_AddRef xpcom/base/nsCOMPtr.cpp:40
1 XUL nsCOMPtr<nsIOutputStreamCallback>::operator= xpcom/base/nsCOMPtr.h:690
1 XUL mozilla::net::TLSTransportLayer::OutputStreamWrapper::AsyncWait netwerk/protocol/http/TLSTransportLayer.cpp:270
2 XUL mozilla::net::TLSTransportLayer::Close netwerk/protocol/http/TLSTransportLayer.cpp:457
3 XUL mozilla::net::WebSocketChannel::CleanupConnection netwerk/protocol/websocket/WebSocketChannel.cpp:2283
4 XUL mozilla::net::WebSocketChannel::DoStopSession netwerk/protocol/websocket/WebSocketChannel.cpp
5 XUL mozilla::net::WebSocketChannel::Notify netwerk/protocol/websocket/WebSocketChannel.cpp
6 XUL {virtual override thunk} netwerk/protocol/websocket/WebSocketChannel.cpp
7 XUL nsTimerImpl::Fire const xpcom/threads/nsTimerImpl.cpp:657
```
There's a decent number of these crashes. The ones I looked at are crashing on poison values, have WebSocketChannel::DoStopSession() on the stack, and are crashing on the main thread.
|
|
1,794,265 | 16,102,965 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
While using GMail with Firefox Nightly
This started happening a few days ago...
Using the NVDA or Narator screen readers
Compose a new message
When you start to edit the message body in the edit box Firefox Nightly freezes
When you type characters they are not displayed or spoken by the screen reader
Actual results:
The GMail compose window remains on the display but there are no updates
The sound effects and spoken feedback are silent
When focus is moved to that edit box there is no audible click
When you type characters they don't appear and are not spoken
You can no longer interact with that tab/window
The browser or computer must be restarted to recover
Task manager often reports Firefox Nightly taking 10% CPU
Expected results:
Normally you can compose the email message in the edit box
When the characters are typed they are displayed and spoken
|
|
1,794,508 | 16,106,293 |
`ePartitionForeignOrDeny` can appear in some third party iframes and thus cause detection failure.
We'll have to update `dom/serviceworkers/test/test_privateBrowsing.html` to cover that.
|
|
1,794,585 | 16,106,799 |
Created attachment 9297971
sign in color.gif
**[Affected Versions]:**
- Firefox RC 106.0 (Build ID: 20221010110315)
**[Affected Platforms]:**
- Windows 10x64
- macOS 11.6.6
- Linux Mint 20.2
**[Prerequisites]:**
- Have a new profile created but not opened yet.
- Have this [user.js file](https://drive.google.com/file/d/1QiB8fip9xK_IbASaUsTn5CxHewpeMafd/view?usp=sharing) copied to the Profile Folder.
- Have a system theme that will have Firefox use the Light theme by default.
**[Steps to reproduce]:**
1. Open the profile from prerequisites using the -p –first-startup syntax.
2. Observe the “Sign in” secondary button from the first “about:welcome” page.
**[Expected result]:**
- The secondary button is white.
**[Actual result]:**
- The secondary button uses the colors of buttons - dark blue for the light theme and light blue for dark theme.
**[Regression Window]:**
Last good revision: b1c9c49674265306fdd706306472fb32a3555eb3
First bad revision: f25371470479192740e16f8b1f8dd385353c9776
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b1c9c49674265306fdd706306472fb32a3555eb3&tochange=f25371470479192740e16f8b1f8dd385353c9776
**[Notes]:**
- Attached is a recording of the issue.
- The issue is also reproducible if the old onboarding is forced using the `browser.aboutwelcome.templateMR` set to `false`.
- The issue is NOT reproducible on Firefox Release 105.0.2 (Build ID: 20221003135607).
|
|
1,795,710 | 16,117,016 |
It appears that the remote-settings CRLite downloads are not cleaned up after they're processed: I've got nearly 1Gb of `-filter` and `-filter.stash` files in my `~/Library/Caches/Firefox/Profiles/xxxxx/settings/security-state/cert-revocations/` directory going back to September 2020.
I don't see a lot of other remote-settings files left in this "cache" spot, and in particular I don't see addon blocklist files which I believe are now using crlite technology.
This came to light from [a fenix issue](https://github.com/mozilla-mobile/fenix/issues/26420) about app data growing even after you clear all the stored user browsing data (history, cache, cookies, etc). A couple of participants identified the cert-revocations directories as huge (480Mb). On Android these files are in the regular profile, not in the separate caches directory. CRLite is not enabled on Fenix, and `about:config` only exists on Nightly, but the participants who identified this were running [Mull](https://divestos.org/index.php?page=our_apps#mull), a Firefox-derived browser using [Arkenfox](https://github.com/arkenfox/user.js) user.js settings. [FWIW I don't think this is the original Fenix reporter's issue]
|
|
1,782,944 | 16,014,771 |
Created attachment 9288273
GetFirefoxKlar_FocusRedirect.gif
**[Notes]**:
- This issue is not reproducible when using en-US locale and DE region.
**[Affected versions]:**
- Firefox Nightly 105.0a1 (Build ID: 20220802214455)
- Firefox Beta 104.0b5 (Build ID: 20220802185803)
- Firefox Release 103.0.1 (Build ID: 20220729222726)
**[Affected Platforms]:**
- macOS 12.3.1
- Windows 10 x64
- Windows 11 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have a DE locale Firefox browser installed/extracted and opened.
- Have the “browser.search.region” pref set to “DE”.
**[Steps to reproduce]:**
1. Restart the browser from prerequisites and open a new private window. (Ctrl+Shift+P)
2. Click the “Download Firefox Klar” button from the promo section.
3. Click the “Download on the App Store” button from the “Get Firefox Focus” modal.
4. Observe the opened link.
**[Expected result]:**
- The “https://app.adjust.com/a8bxj8j?campaign=firefox-desktop&adgroup=pb&creative=focus-omc172&redirect=https%3A%2F%2Fapps.apple.com%2Fde%2Fapp%2Fklar-by-firefox%2Fid1073435754” URL and the Firefox Klar app is displayed on the page.
**[Actual result]:**
- The “Download on the App Store” redirects to the “https://apps.apple.com/us/app/firefox-focus-privacy-browser/id1055677337” URL and the Firefox Focus app is displayed on the page.
**[Additional Notes]:**
- This issue is also reproducible when clicking the “GET IT ON Google Play" button. It redirects to the “https://play.google.com/store/apps/details?id=org.mozilla.focus&referrer=adjust_reftag%3DcaXHXSa24J49B%26utm_source%3Dproduct-owned%26utm_campaign%3Dfirefox-desktop%26utm_content%3Dpb%26utm_term%3Dfocus-omc172%26utm_medium%3Dreferral” URL and the Firefox Focus app is displayed on the page instead of Firefox Klar.
- Also, sometimes the App store page takes a long time until it is fully loaded.
- Attached is a screen recording of the issue.
|
|
1,783,197 | 16,016,630 |
Created attachment 9288489
image (1).png
**Affected versions**
* Nightly 105.0a1
**Affected platforms**
* Windows 10 x64
* Ubuntu 22
*macOS 12
**Steps to reproduce**
1. Launch Firefox with browser.tabs.firefox-view=true
2. Click to open Firefox view page
3. Turn ON High-Contrast
4. Hover the Firefox View tab collapse arrows
**Expected result**
* The arrows are visible with High Contrast
**Actual result**
* Firefox View collapse arrows are not visible with High Contrast on hover
**Regression range**
New feature
**Additional notes**
* On Ubuntu 22 the issue is seen with Firefox Light Theme and Ubuntu High Contrast Theme
|
|
1,783,552 | 16,018,337 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.81 Safari/537.36 Edg/104.0.1293.47
Steps to reproduce:
Selected to download headers only, when downloading rest of the message:
TypeError: this.runningUri.SetUrlState is not a function 2 Pop3Client.jsm:132:21
About time to have this covered in a test or testplan
|
|
1,783,887 | 16,022,379 |
**Found in**
* Firefox 105.0a1
**Affected versions**
* Firefox 105.0a1
**Affected platforms**
* macOS 11.6
**Preconditions**
In about:config set:
"browser.theme.colorway-closet" to true
"browser.tabs.firefox-view" to true
**Steps to reproduce**
1. Open "Colorways closet" from Fxview or from about:addons
**Expected result**
Colorways closet should be correctly displayed.
**Actual result**
Colorways closet is displayed minimized with unnecessary scrolling bar.
**Regression range**
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1875b970dc64011b8a0b093ed432d0117d9758cb&tochange=dba4dc940ca9c180ac5ecc3011eb9761a3ca5026
|
|
1,783,892 | 16,022,422 |
Created attachment 9289059
Get Firefox for mobile sends to sync page with QR code.gif
Affected versions:
Nightly 105.0a1 (2022-08-09)
Affected platforms:
Windows 10 64-bit
Preconditions:
The user is already logged in to the browser with a Fx account.
Steps to reproduce:
1. Click the Firefox view icon on the top of the browser's page before the Tabs bar.
2. Click the "Get Firefox for mobile" button.
3. Observe the page displayed.
Actual result:
The "Sync Firefox on your phone or tablet" page is displayed.
Expected result:
The "Download Firefox on your phone or tablet" page is displayed.
|
|
1,784,019 | 16,023,414 |
Created attachment 9289192
fx view session restore.webm
**Found in**
- Firefox 105.0a1
**Affected versions**
- Firefox 105.0a1
**Affected platforms**
- Ubuntu 22.04
- macOS 11
- Windows 10
**Steps to reproduce**
1. Launch Firefox with browser.tabs.firefox-view=true
2. Access some random tabs to have them on background and focus Firefox view page
3. Close Firefox from the menu and restart it with the same profile
4. Have the focus over Firefox view and select Menu -> History -> Restore previous session
**Expected result**
- The previous session is restored without issues
**Actual result**
- Firefox closes unexpectedly without any warnings
**Regression range**
- New feature.
**Additional notes**
- The issue can be seen in the attachment.
|
|
1,784,055 | 16,023,630 |
Created attachment 9289234
wrong message displayed.gif
Affected versions:
Nightly 105.0a1 (2022-08-09)
Affected platforms:
Windows 10 64-bit
Preconditions:
The user is already logged in to the browser with a Fx account.
The user has gone through the connect another device flow.
Steps to reproduce:
1. Go to about:preferences#sync page and click the "Change" button under Syncing options.
2. Click the "Disconnect..." button and in the modal click "Disconnect" again.
3. Click the "Firefox View" icon and observe the message displayed.
Actual result:
The "Sit tight while your tabs sync. It'll be just a moment." message is displayed with a loading wheel.
Expected result:
The "Turn on syncing to continue" message is displayed with "Turn on sync in settings" button.
|
|
1,784,294 | 16,025,173 |
Created attachment 9289484
no syncing when switching_openin tabs.gif
Affected versions:
Nightly 105.0a1 (2022-08-10)
Affected platforms:
Windows 10 64-bit
macOS 10.14
Ubuntu 20.04
Preconditions:
The user is already logged in to the browser with a Fx account.
The user has a mobile device connected.
Steps to reproduce:
1. Click the Firefox view tab on desktop.
2. On the mobile device open more than 3 pages in new tabs.
3. Go back to desktop, open a new tab or window/ load a new page in an existing tab/ switch tabs.
4. Go back to Firefox view and observe the Tab pickup section.
Actual result:
The Tab pickup section is not updated with the last active tabs from mobile.
Expected result:
The Tab pickup section is updated with the last active tabs from mobile.
Note: The Tab pickup content is updated only when the user clicks the Firefox account button in the toolbar or Sync now button from the Firefox account drop-down menu.
|
|
1,785,050 | 16,031,841 |
The attached testcase crashes on mozilla-central revision 20220814-64a12fec281c (build with (metadatabuildFlags not available)).
For detailed crash information, see attachment.
To reproduce the issue, perform the following steps:
1. Download the attached testcase, save as "test.bin".
2a. Build with `--enable-fuzzing` (requires Clang and ASan, also build gtests using `./mach gtest dontruntests`).
2b. Alternatively you can download builds from TC using `python -mfuzzfetch -a --fuzzing -n build --target firefox gtest` (see https://github.com/MozillaSecurity/fuzzfetch).
3. Run `FUZZER=NetworkHttp2ProxyHttp2 build/firefox test.bin`
Marking s-s as this could potentially be a security issue (e.g. use-after-free or double-free).
|
|
1,785,311 | 16,033,947 |
Steps to reproduce:
1. Open a document with a `<textarea>` or `<input>`. Sample: `data:text/html,<div contenteditable>text node</div><textarea>textarea</textarea><input value="text box">`. (The contenteditable is *not* affected, and is just there for comparison.)
2. Open the find bar (Ctrl+F).
3. Ensure “Highlight All” is enabled.
4. Search for something that matches inside the textarea/input (e.g. “text” in my sample).
5. Select the textarea/input.
6. Begin composition, e.g. by pressing Ctrl+Shift+U (which normally inserts an underlined “u” while waiting for you to enter the code point number). (I first found it with a Compose key, which normally inserts an underlined “·” while waiting for the compose sequence.)
7. Observe the page crash.
Consistently reproducible. Uncertain if it’s a regression or not: I’m not in the habit of using find in textareas, though I do use my Compose key extremely regularly.
Crash report: https://crash-stats.mozilla.org/report/index/449c53d6-82ca-495f-9919-2c3e70220817
Reason: ```SIGSEGV / SEGV_MAPERR```
Top 10 frames of crashing thread:
```
0 libxul.so mozilla::EditorBase::InsertTextIntoTextNodeWithTransaction editor/libeditor/EditorBase.cpp:3067
1 libxul.so mozilla::EditorBase::InsertTextWithTransaction editor/libeditor/EditorBase.cpp:2892
2 libxul.so mozilla::TextEditor::HandleInsertText editor/libeditor/TextEditSubActionHandler.cpp:473
3 libxul.so mozilla::EditorBase::InsertTextAsSubAction editor/libeditor/EditorBase.cpp:6089
4 libxul.so mozilla::EditorBase::OnCompositionChange editor/libeditor/EditorBase.cpp:3674
5 libxul.so mozilla::EditorEventListener::HandleChangeComposition editor/libeditor/EditorEventListener.cpp:1071
6 libxul.so mozilla::EventTargetChainItem::HandleEvent dom/events/EventDispatcher.cpp:348
7 libxul.so mozilla::EventTargetChainItem::HandleEventTargetChain dom/events/EventDispatcher.cpp:550
8 libxul.so mozilla::EventTargetChainItem::HandleEventTargetChain dom/events/EventDispatcher.cpp:630
9 libxul.so mozilla::EventDispatcher::Dispatch dom/events/EventDispatcher.cpp:1119
```
|
|
1,789,298 | 16,062,877 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0
Steps to reproduce:
1. Open any website you have the login credentials stored.
2. Open the autofill menu for a login form.
3. Press "Del" key.
Actual results:
It deletes the selected credentials from the password manager instantly without a prompt, and also instantly removes it from the cloud if you have the sync on.
So 1 accidental key press completely purges your credentials from your account and all devices.
Expected results:
At least have a prompt, like when deleting the credentials from the password manager.
|
|
1,789,371 | 16,063,349 |
Created attachment 9293252
crash.html
I found in Firefox 32-bit after filling with a lot of memory (approximate 3000MB) then create a lot new Worker construction afterward call webgl `getExtension('OES_vertex_array_object')` repeatedly Firefox able to crash on 0xe5e5e5f5 address in mozilla::ClientWebGLContext::GetExtension.
I observe on stdout before Firefox crash it show `WARNING: Call to mmap failed: Operation not permitted` and `Failed to allocate internal command buffer.`. It's look like after Firefox freed the memory, but it fail to allocate new memory on the target address due to low address spaces, so when `getExtension('OES_vertex_array_object')` is called it still point to freed memory which leads to UAF.
## Reproducible on:
- Firefox Nightly 106.0a1 (2022-09-05) (32-bit) on Arch Linux using AMD Ryzen 7 5700G
- Firefox Nightly 106.0a1 (2022-09-05) (32-bit) on Arch Linux using Intel i5-1035G1
- Firefox 104.0.1 (32-bit) on Arch Linux using AMD Ryzen 7 5700G
- Firefox 104.0.1 (32-bit) on Arch Linux using Intel i5-1035G1
## Steps to reproduce:
1. Open Firefox 32-bit
2. Visit attached crash.html
3. Firefox crashed in `mozilla::ClientWebGLContext::GetExtension` on address `0xe5e5e5f5`
|
|
1,789,652 | 16,065,378 |
STR:
1. Click on a recently closed tab
Outcome:
Focus switches to a completely unrelated tab and the tab disappears from the Recently Closed list
Expected Results:
The expected tab shows up
106.0a1 (2022-09-06) on MacOS
|
|
1,789,885 | 16,067,061 |
I unfortunately don't have STR; but I just noticed that the Firefox View page in all of my Firefox windows on my linux laptop are currently showing:
`Sit tight while your tabs sync. It’ll be just a moment.`
...and have been showing it for about 10 minutes. (I noticed it 10 minutes ago and it's still like that.)
Meanwhile `about:sync-log` shows that I had a successful sync 11 minutes ago (from 1 minute before I thought to check Firefox View and noticed this issue).
Also, `History | Synced Tabs` shows me a nice list of up-to-date synced tabs.
Nothing particularly interesting shows up in browser console or in web console for my Firefox View tabs. New windows & new `about:firefoxview` tabs show this issue as well.
So it looks like there's some sort of mismatch where Firefox View mistakenly thinks that we're syncing but in fact we're not. (?)
|
|
1,789,974 | 16,067,893 |
**[Notes]:**
- This issue is reproducible if the "Pin Private Window" action is taken from the existing Onboarding modals.
**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220908213354
**[Affected Platforms]:**
- Windows 10 x64
**[Prerequisites]:**
- The "Private Window" shortcut is not pinned to the taskbar.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Open a new "Private Window".
3. Click the "Pin to taskbar" button and observe the behavior.
**[Expected result]:**
- The "Private Window" shortcut is pinned to the taskbar.
**[Actual result]:**
- The "Private Window" shortcut is NOT pinned to the taskbar and the following error is displayed in the "Browser Console":
`[Exception... "Failure" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "<unknown>" data: no] ShellService.jsm:460
pinToTaskbar resource:///modules/ShellService.jsm:460
AsyncFunctionThrow self-hosted:885`
**[Regression Window]:**
- Considering that this issue is not reproducible with the Firefox Nightly build from 09/07/2022 using the Mozregression tool I have managed to find the following regression window:
Last good revision: bea1e1ba4a14e676e4ebefa371d8fb5fea9d6001
First bad revision: b1462bbc7934f45eff16184644a1eaca75b044c0
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=bea1e1ba4a14e676e4ebefa371d8fb5fea9d6001&tochange=b1462bbc7934f45eff16184644a1eaca75b044c0
From the pushlog it seems that Bug 1782295 may have caused this regression.
@Ben, could you please take a look over this issue?
**[Additional Notes]:**
- This issue is not reproducible with the regular "Firefox" shortcut.
- Attached a screen recording of the issue.
|
|
1,789,991 | 16,067,998 |
Created attachment 9293894
Screenshot1.jpg
**Note**
*Issue reproduces only on Win7
**Found in**
* 106.0a1(20220908213354)
**Affected versions**
* 106.0a1(20220908213354)
**Tested platforms**
* Affected platforms:Win7
* Unaffected platforms: Win10, Ubuntu, Mac
**Steps to reproduce**
1. Uninstall all existing Firefox builds, delete all profiles and registry.
2. Do a Nightly clean install with the latest build.
3. Check all Firefox icons from Start - All Programs menu.
**Expected result**
* Only one Private icon for Firefox should be displayed.
**Actual result**
* There are two Private icons for Firefox on All programs.
**Regression range**
* First bad build: we saw the issue starting with build 106.0a1(20220908213354)
**Additional notes**
* Issue also reproducing for localizations (French-confirmed) and only on Win7.
|
|
1,790,407 | 16,072,169 |
**Found in**
* Nightly 106.0a1
**Affected versions**
* Nightly 106.0a1
**Tested platforms**
* Affected platforms: Windows 10x64, Ubuntu 18.4 and macOS 10.12.6
**Steps to reproduce**
1. Launch Firefox
2. Go to Firefox View tab pick up
3. Click Continue button to sign in with FxA account
4. Sign In with account
5. Return to Firefox View and click Close on the mobile pick up card button
**Expected result**
* Mobile pick up message card is closed.
**Actual result**
* Close button is not working for the mobile pick up card
**Regression range**
* First bad: 106.0a1 (2022-09-09)
* Last good: 106.0a1 (2022-09-08)
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2b0f7a20d14a3b1c4ea192a85028288c8b3d2df7&tochange=0e3963842e57b86dd0fb9e5f2e8eb8eab02192ed
* Potentially regressed by: Bug 1789226 - Show zap gradient border for tab pickup cards. r=sclements
|
|
1,791,163 | 16,077,283 |
Created attachment 9295051
mr 105.gif
**[Affected Versions]:**
- Firefox RC 2 105.0 (Build ID: 20220915150737)
- Firefox Nightly 105.0a1 (Build ID: 20220802094116)
**[Affected Platforms]:**
- Windows 10
- macOS 11.6.6
- Linux Mint 20.2
**[Prerequisites]:**
- If using a build other than Nightly, have the “channel-prefs” file of the build modified to have "app.update.channel" set to “nightly”.
- Have updates disabled (e.g. by selecting “Check for updates but let you choose to install them” from “about:preferences”).
**[Steps to reproduce]:**
1. Open the browser.
2. Open “about:config” and set the following prefs:
` messaging-system.rsexperimentloader.collection_id` set to `nimbus-preview`.
`messaging-system.log` set to `all`
3. Open the Multiprocess Browsing Console (using Ctrl/command + Shift + J).
4. Restart the browser (by using Ctrl/command + Alt + R with the Browsing Console focused).
5. Open “about:studies” and observe the page.
6. Focus the Browsing Console and observe the messages displayed for “qa-nightly-firefox-mr-existing-user-experience”.
**[Expected result]:**
Step 5. The “QA Nightly Firefox MR Existing User Experience” study is displayed in “Active studies”.
Step 6. There is a message displayed stating that “qa-nightly-firefox-mr-existing-user-experience” matched.
**[Actual result]:**
Step 5. The “QA Nightly Firefox MR Existing User Experience” study is not displayed.
Step 6. There are messages displayed stating that
- “qa-nightly-firefox-mr-existing-user-experience did not validate”
- properties do “not match additional properties schema.”
**[Notes]:**
- The Nightly version of the build displays the message that “Experiment qa-nightly-firefox-mr-existing-user-experience has unknown featureId: majorRelease2022”.
- The issue is not reproducible for Firefox Nightly 106.0a1 (Build ID: 20220915171049)
- Attached is a recording of the issue.
|
|
1,791,191 | 16,077,496 |
Created attachment 9295073
bad.pdf
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0
Steps to reproduce:
Open bad.pdf
Actual results:
No text is displayed compared to good.pdf
Expected results:
bad.pdf should look like good.pdf, i. e. display "Lohnabrechnung"
|
|
1,778,951 | 15,980,239 |
Created attachment 9284891
broken_console.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
Steps to reproduce:
Using Firefox 102/103/104:
1) extract extension
2) load it from "about:debugging" page
3) inspect background script by clicking the "Inspect" button or by opening: "about:devtools-toolbox?id=bugzilla%40broken.reload&type=extension"
4) you will see some console logs that should update every 5 seconds
5) wait 10 seconds
Actual results:
The logs stops updating after 10 seconds (second reload).
Additionally, console is now not working and executing anything inside it won't print any results anymore.
Expected results:
The console should re-print the logs every 5 seconds.
This is a regression, it works in Firefox ESR 91 but not it current version.
This makes addon development very bad because it forces developer to close and reopen background script tab over and over.
|
|
1,779,138 | 15,981,568 |
I'm getting these about 50 seconds apart.
Here's a stack:
```
19.94 s 100.0% 0 s mozilla::detail::RunnableFunction<mozilla::MemoryTelemetry::GatherTotalMemory()::$_3>::Run()
19.94 s 100.0% 0 s nsMemoryReporterManager::ResidentUnique(unsigned int)
19.94 s 99.9% 11.00 ms ResidentUniqueDistinguishedAmount(long long*, unsigned int) (.llvm.6731204511831033690)
19.91 s 99.8% 15.00 ms mach_vm_region
19.85 s 99.5% 17.00 ms mach_msg
19.84 s 99.4% 19.84 s mach_msg_trap
```
|
|
1,780,188 | 15,991,005 |
**[Notes]:**
- This issue is reproducible only using the Release Candidate build; on Nightly 104.0a1 and Beta 103.0b9 builds the autofill impressions are correctly triggered and displayed in the `about:telemetry` page.
**[Affected versions]:**
- Firefox RC 103, Build ID: 20220718155818
**[Affected platforms]:**
- Windows 10 x64
- macOS 12.4
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have Firefox RC 103 (en* build) on your computer.
- Have the following [user.js](https://drive.google.com/file/d/1XRWXb4DQHGfPmMdeuHMuZ3rdyueB-WUx/view?usp=sharing) downloaded on your computer.
- Have the `browser.search.region` pref set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to the Profile Folder from `about:support` page and paste the user.js file from the prerequisites.
2. Restart the browser and open a new tab.
3. Type `moz` characters in the Address Bar.
4. After the `mozilla.org/` domain autofills, press the `Enter` key
5. Navigate to `about:telemetry` in the new tab.
6. Search for `urlbar.impression.autofill_origin` scalar.
**[Expected result]:**
- The `urlbar.impression.autofill_origin` scalar is displayed with `1` as value.
**[Actual result]:**
- The `urlbar.impression.autofill_origin` scalar is **not** displayed.
**[Additional notes]:**
- This issue is also reproducible with the following impressions:
- urlbar.impression.autofill_adaptive
- urlbar.impression.autofill_url
- urlbar.impression.autofill_about
- I have also looked over the [Probe Dictionary](https://probes.telemetry.mozilla.org/?search=urlbar.impression.autofill) and I have noticed that the autofill impressions are recorded only in Nightly and Beta starting with 103 version. Is it intended not having them on the Release builds?
- [Here](https://drive.google.com/file/d/1fM4QQk1L2c65F0bveknXCNeLJhlrH2ev/view?usp=sharing) is a screen recording with the issue.
|
|
1,781,094 | 15,999,640 |
The images at https://pohrebnictvodvonc.sk/smutocne-oznamy no longer load, and mozregression pointed me to https://phabricator.services.mozilla.com/D141272.
|
|
1,781,759 | 16,005,262 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
Embedded a video in an iFrame. Format is mp4. If I play the video with a normal video tag it works fine but not if its inside an iFrame. See below
https://jsfiddle.net/jonny_fux/d2b6c5af/11/
Actual results:
Error: No Video with supported format and MIME type found
Expected results:
The video should be played. That works in Safari and Chromium Browsers.
|
|
1,781,823 | 16,005,568 |
Crash report: https://crash-stats.mozilla.org/report/index/5c455015-7b51-4fc9-b65c-427e80220727
This crash looks like a regression in Fenix 103.
MOZ_CRASH Reason: ```Global Glean object not initialized```
Top 10 frames of crashing thread:
```
0 libxul.so RustMozCrash mozglue/static/rust/wrappers.cpp:18
1 libxul.so mozglue_static::panic_hook mozglue/static/rust/lib.rs:91
2 libxul.so core::ops::function::Fn::call library/core/src/ops/function.rs:70
3 libxul.so std::panicking::rust_panic_with_hook library/std/src/panicking.rs:702
4 libxul.so std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:588
5 libxul.so std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:138
6 libxul.so rust_begin_unwind library/std/src/panicking.rs:584
7 libxul.so core::panicking::panic_fmt library/core/src/panicking.rs:143
8 libxul.so core::panicking::panic_display library/core/src/panicking.rs:72
9 libxul.so core::panicking::panic_str library/core/src/panicking.rs:56
```
|
|
1,781,936 | 16,006,259 |
Steps to reproduce:
1. Open Fenix (or GeckoViewExample)
2. Enable strict antitracking/ETP (to enable the content blocker).
3. Navigate to rottentomatoes.com
4. Confirm that tracking content is being blocked. In Fenix this can be easily seen in the lock icon in the URL bar in the details, whereas in GeckoViewExample, a small gap at the top of the page (where an ad will otherwise appear) will remain empty when blocking is working.
5. Navigate on the same tab to twitter.com
6. On Fenix, confirm that tracking content is NOT being blocked as it should be (on GVE there is no simple UI/way to tell).
7. Navigate on the same tab to rottentomatoes.com
8. Confirm that tracking content is still NOT being blocked (see step 4 for details).
Very curiously, not all websites seem to trigger this bug. Twitter.com and Facebook.com do, but others may not. However, once it is broken, the user must toggle a setting in the UI like strict mode (more info on this shortly), or open a new tab to get it working again.
This was originally reported in https://github.com/mozilla-mobile/fenix/issues/26059, and
several of us have been digging around to discover what's happening. We're not sure when the bug regressed, or what regressed it; it looks like it may have been a surprisingly long time ago.
Note that this affects more than just the content blocker. These features are also broken:
- the anti-tracking content blocker used in Strict mode (useTrackingProtection flag)
- PWA display mode support (displayMode flag)
- display desktop page mode (viewportMode flag)
- toggle page javascript on/off (allowJavascript flag)
- custom user-agent string (customUserAgent flag)
Evidently browsingContexts need to have these flags set by GeckoView to keep these features working. The only place where this seems to be done is in [GeckoViewSettings.onSettingsUpdate()](https://searchfox.org/mozilla-central/source/mobile/android/modules/geckoview/GeckoViewSettings.jsm#68), but this is not called during navigations, only when a tab is first created, or when a setting is changed in the UI.
I've made a trivial patch which also triggers onSettingsUpdate when onLocationChange begins to be handled, which fixes this. I'm not at all sure if it's the best fix here, but it's a start.
As for why this broke, I suspect that one of these things had to be true at some point, otherwise the current code would never have worked:
- onSettingsUpdate was once called each time a navigation happened, and so was able to update the browsingContext.
- The flags were once carried over to new browsingContexts across navigations in some lower-level code, and so did not have to be re-set.
- browsingContexts somehow did not change before, so the flags did not need to be re-set in the first place.
(Special thanks also to owlish, tihuang, and amoya for their help with the investigations here as well!)
|
|
1,796,586 | 16,122,740 |
Created attachment 9299490
tabalanche-1.1.0.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
1. Download extensions - `tabalanche-1.1.0.zip` and `tabalanche-no-pouchdb-1.1.0.zip` in the attachment
2. Turn off signature verification (about:config -> change xpinstall.signatures.required to false)
3. Install extensions (Ctrl-Shift-A -> Top-right gear icon -> Install addon from files)
4. Open `about:debugging#/runtime/this-firefox`
5. Wait until all background scripts are stopped. https://i.imgur.com/B02QYcl.png
6. Restart the browser.
Actual results:
The extension opens a new tab `http://example.com/no-pouchdb`
Expected results:
We should get two tabs. The one with pouchdb should also open a new tab `http://example.com` at startup.
|
|
1,796,901 | 16,125,064 |
```js
gcslice(0);
evalcx("lazy");
abortgc();
```
```
(gdb) bt
#0 js::gc::GCRuntime::sweepZones (this=this@entry=0x7ffff6c18778, gcx=gcx@entry=0x7ffff6c18790, destroyingRuntime=true) at /home/skygentoo/trees/mozilla-central/js/src/gc/GC.cpp:2083
#1 0x00005555575ed24f in js::gc::GCRuntime::incrementalSlice (this=this@entry=0x7ffff6c18778, budget=..., reason=reason@entry=JS::GCReason::DESTROY_RUNTIME, budgetWasIncreased=false) at /home/skygentoo/trees/mozilla-central/js/src/gc/GC.cpp:3356
#2 0x00005555575f0114 in js::gc::GCRuntime::gcCycle (this=this@entry=0x7ffff6c18778, nonincrementalByAPI=false, budgetArg=..., reason=reason@entry=JS::GCReason::DESTROY_RUNTIME) at /home/skygentoo/trees/mozilla-central/js/src/gc/GC.cpp:3841
#3 0x00005555575f12c6 in js::gc::GCRuntime::collect (this=this@entry=0x7ffff6c18778, nonincrementalByAPI=<optimized out>, budget=..., reason=reason@entry=JS::GCReason::DESTROY_RUNTIME) at /home/skygentoo/trees/mozilla-central/js/src/gc/GC.cpp:4029
#4 0x00005555575c6d48 in js::gc::GCRuntime::gc (this=0x7ffff6c18778, options=JS::GCOptions::Shutdown, reason=JS::GCReason::DESTROY_RUNTIME) at /home/skygentoo/trees/mozilla-central/js/src/gc/GC.cpp:4106
#5 0x000055555708eef1 in JSRuntime::destroyRuntime (this=0x7ffff6c18000) at /home/skygentoo/trees/mozilla-central/js/src/vm/Runtime.cpp:266
#6 0x0000555556f3d056 in js::DestroyContext (cx=cx@entry=0x7ffff6c2a100) at /home/skygentoo/trees/mozilla-central/js/src/vm/JSContext.cpp:225
#7 0x00005555572a470a in JS_DestroyContext (cx=0x7ffff7c12a40 <_IO_stdfile_2_lock>, cx@entry=0x7ffff6c2a100) at /home/skygentoo/trees/mozilla-central/js/src/jsapi.cpp:400
#8 0x0000555556c0cd07 in main::$_3::operator() (this=<optimized out>) at /home/skygentoo/trees/mozilla-central/js/src/shell/js.cpp:12120
#9 mozilla::ScopeExit<main::$_3>::~ScopeExit (this=<optimized out>) at /home/skygentoo/shell-cache/js-dbg-64-linux-x86_64-321d39a49683/objdir-js/dist/include/mozilla/ScopeExit.h:106
#10 main (argc=<optimized out>, argv=<optimized out>) at /home/skygentoo/trees/mozilla-central/js/src/shell/js.cpp:12330
(gdb)
```
```
The first bad revision is:
changeset: https://hg.mozilla.org/mozilla-central/rev/2815b08bfbd2
user: Jon Coppeard
date: Mon Oct 17 17:09:07 2022 +0000
summary: Bug 1791975 - Don't sweep realms that were allocated during incremental GC r=jandem
```
Run with `--fuzzing-safe --no-threads --no-baseline --no-ion`, compile with `AR=ar sh ./configure --enable-debug --with-ccache --enable-nspr-build --enable-ctypes --enable-debug-symbols --enable-gczeal --enable-rust-simd --disable-tests`, tested on m-c rev 321d39a49683.
Setting s-s just-in-case. Jon, is bug 1791975 a likely regressor? FYI bug 1791975 seems to be a restricted bug.
|
|
1,797,202 | 16,128,968 |
The code that loads messages from Nimbus explicitly [checks for an experiment](https://searchfox.org/mozilla-central/rev/12a18f7e112a4dcf88d8441d439b84144bfbe9a3/browser/components/newtab/lib/ASRouter.jsm#361), so if there is a rollout, the message wont be ingested.
|
|
1,797,553 | 16,131,892 |
+++ This bug was initially created as a clone of Bug #1795349 +++
In order for fxms-message-1 to work correctly as an FxMS experiment feature (which is required to use it in the Bookmarks Import experiment for 107), it needs to be on a special list in ASRouter.
|
|
1,797,685 | 16,132,675 |
The attached testcase crashes on mozilla-central revision 20221027-68d82e6cb0c9 (build with asan-opt, run with --no-threads test.js).
Backtrace:
```
==32005==ERROR: AddressSanitizer: heap-use-after-free on address 0x60c000021a20 at pc 0x565483e5deeb bp 0x7ffd54b50b70 sp 0x7ffd54b50b68
READ of size 8 at 0x60c000021a20 thread T0
#0 0x565483e5deea in (anonymous namespace)::FunctionCompiler::delegatePadPatches(mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy> const&, unsigned int) js/src/wasm/WasmIonCompile.cpp:2836:35
#1 0x565483e2e15f in EmitDelegate((anonymous namespace)::FunctionCompiler&) js/src/wasm/WasmIonCompile.cpp:3800:12
#2 0x565483de82f8 in EmitBodyExprs((anonymous namespace)::FunctionCompiler&) js/src/wasm/WasmIonCompile.cpp:5891:14
#3 0x565483de6d56 in js::wasm::IonCompileFunctions(js::wasm::ModuleEnvironment const&, js::wasm::CompilerEnvironment const&, js::LifoAlloc&, mozilla::Vector<js::wasm::FuncCompileInput, 8ul, js::SystemAllocPolicy> const&, js::wasm::CompiledCode*, mozilla::UniquePtr<char [], JS::FreePolicy>*) js/src/wasm/WasmIonCompile.cpp:7103:12
#4 0x565483da372d in ExecuteCompileTask(js::wasm::CompileTask*, mozilla::UniquePtr<char [], JS::FreePolicy>*) js/src/wasm/WasmGenerator.cpp:664:12
#5 0x565483da398d in js::wasm::ModuleGenerator::locallyCompileCurrentTask() js/src/wasm/WasmGenerator.cpp:719:8
#6 0x565483da4795 in js::wasm::ModuleGenerator::finishFuncDefs() js/src/wasm/WasmGenerator.cpp:850:24
#7 0x565483d7b421 in bool DecodeCodeSection<js::wasm::Decoder>(js::wasm::ModuleEnvironment const&, js::wasm::Decoder&, js::wasm::ModuleGenerator&) js/src/wasm/WasmCompile.cpp:686:13
#8 0x565483d7addc in js::wasm::CompileBuffer(js::wasm::CompileArgs const&, js::wasm::ShareableBytes const&, mozilla::UniquePtr<char [], JS::FreePolicy>*, mozilla::Vector<mozilla::UniquePtr<char [], JS::FreePolicy>, 0ul, js::SystemAllocPolicy>*, JS::OptimizedEncodingListener*) js/src/wasm/WasmCompile.cpp:708:8
#9 0x565483dfa5da in js::WasmModuleObject::construct(JSContext*, unsigned int, JS::Value*) js/src/wasm/WasmJS.cpp:1713:7
#10 0x56548270ee19 in CallJSNative js/src/vm/Interpreter.cpp:459:13
[...]
#22 0x56548237127c in main js/src/shell/js.cpp:12320:12
0x60c000021a20 is located 32 bytes inside of 128-byte region [0x60c000021a00,0x60c000021a80)
freed by thread T0 here:
#0 0x56548231e656 in __interceptor_realloc /builds/worker/fetches/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3
#1 0x565483e5c176 in js_arena_realloc dist/include/js/Utility.h:402:10
#2 0x565483e5c176 in js_pod_arena_realloc<js::jit::MControlInstruction *> dist/include/js/Utility.h:608:26
#3 0x565483e5c176 in maybe_pod_arena_realloc<js::jit::MControlInstruction *> dist/include/js/AllocPolicy.h:42:12
#4 0x565483e5c176 in pod_arena_realloc<js::jit::MControlInstruction *> dist/include/js/AllocPolicy.h:55:12
#5 0x565483e5c176 in pod_realloc<js::jit::MControlInstruction *> dist/include/js/AllocPolicy.h:80:12
#6 0x565483e5c176 in growTo dist/include/mozilla/Vector.h:305:21
#7 0x565483e5c176 in mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy>::growStorageBy(unsigned long) dist/include/mozilla/Vector.h:1066:10
#8 0x565483e5bede in growByUninitialized dist/include/mozilla/Vector.h:1172:9
#9 0x565483e5bede in bool mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy>::emplaceBack<js::jit::MControlInstruction*&>(js::jit::MControlInstruction*&) dist/include/mozilla/Vector.h:765:10
#10 0x565483e5bda8 in (anonymous namespace)::FunctionCompiler::addPadPatch(js::jit::MControlInstruction*, unsigned long) js/src/wasm/WasmIonCompile.cpp:2813:23
#11 0x565483e5ddf6 in (anonymous namespace)::FunctionCompiler::delegatePadPatches(mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy> const&, unsigned int) js/src/wasm/WasmIonCompile.cpp:2837:12
#12 0x565483e2e15f in EmitDelegate((anonymous namespace)::FunctionCompiler&) js/src/wasm/WasmIonCompile.cpp:3800:12
#13 0x565483de82f8 in EmitBodyExprs((anonymous namespace)::FunctionCompiler&) js/src/wasm/WasmIonCompile.cpp:5891:14
#14 0x565483de6d56 in js::wasm::IonCompileFunctions(js::wasm::ModuleEnvironment const&, js::wasm::CompilerEnvironment const&, js::LifoAlloc&, mozilla::Vector<js::wasm::FuncCompileInput, 8ul, js::SystemAllocPolicy> const&, js::wasm::CompiledCode*, mozilla::UniquePtr<char [], JS::FreePolicy>*) js/src/wasm/WasmIonCompile.cpp:7103:12
#15 0x565483da372d in ExecuteCompileTask(js::wasm::CompileTask*, mozilla::UniquePtr<char [], JS::FreePolicy>*) js/src/wasm/WasmGenerator.cpp:664:12
#16 0x565483da398d in js::wasm::ModuleGenerator::locallyCompileCurrentTask() js/src/wasm/WasmGenerator.cpp:719:8
#17 0x565483da4795 in js::wasm::ModuleGenerator::finishFuncDefs() js/src/wasm/WasmGenerator.cpp:850:24
#18 0x565483d7b421 in bool DecodeCodeSection<js::wasm::Decoder>(js::wasm::ModuleEnvironment const&, js::wasm::Decoder&, js::wasm::ModuleGenerator&) js/src/wasm/WasmCompile.cpp:686:13
#19 0x565483d7addc in js::wasm::CompileBuffer(js::wasm::CompileArgs const&, js::wasm::ShareableBytes const&, mozilla::UniquePtr<char [], JS::FreePolicy>*, mozilla::Vector<mozilla::UniquePtr<char [], JS::FreePolicy>, 0ul, js::SystemAllocPolicy>*, JS::OptimizedEncodingListener*) js/src/wasm/WasmCompile.cpp:708:8
#20 0x565483dfa5da in js::WasmModuleObject::construct(JSContext*, unsigned int, JS::Value*) js/src/wasm/WasmJS.cpp:1713:7
#21 0x56548270ee19 in CallJSNative js/src/vm/Interpreter.cpp:459:13
[...]
#33 0x56548237127c in main js/src/shell/js.cpp:12320:12
previously allocated by thread T0 here:
#0 0x56548231e38e in malloc /builds/worker/fetches/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:69:3
#1 0x565483e5c25c in js_arena_malloc dist/include/js/Utility.h:366:10
#2 0x565483e5c25c in js_pod_arena_malloc<js::jit::MControlInstruction *> dist/include/js/Utility.h:576:26
#3 0x565483e5c25c in maybe_pod_arena_malloc<js::jit::MControlInstruction *> dist/include/js/AllocPolicy.h:33:12
#4 0x565483e5c25c in pod_arena_malloc<js::jit::MControlInstruction *> dist/include/js/AllocPolicy.h:46:12
#5 0x565483e5c25c in pod_malloc<js::jit::MControlInstruction *> dist/include/js/AllocPolicy.h:72:12
#6 0x565483e5c25c in mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy>::convertToHeapStorage(unsigned long) dist/include/mozilla/Vector.h:1025:30
#7 0x565483e5bede in growByUninitialized dist/include/mozilla/Vector.h:1172:9
#8 0x565483e5bede in bool mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy>::emplaceBack<js::jit::MControlInstruction*&>(js::jit::MControlInstruction*&) dist/include/mozilla/Vector.h:765:10
#9 0x565483e5bda8 in (anonymous namespace)::FunctionCompiler::addPadPatch(js::jit::MControlInstruction*, unsigned long) js/src/wasm/WasmIonCompile.cpp:2813:23
#10 0x565483e5ddf6 in (anonymous namespace)::FunctionCompiler::delegatePadPatches(mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy> const&, unsigned int) js/src/wasm/WasmIonCompile.cpp:2837:12
#11 0x565483e2e15f in EmitDelegate((anonymous namespace)::FunctionCompiler&) js/src/wasm/WasmIonCompile.cpp:3800:12
#12 0x565483de82f8 in EmitBodyExprs((anonymous namespace)::FunctionCompiler&) js/src/wasm/WasmIonCompile.cpp:5891:14
#13 0x565483de6d56 in js::wasm::IonCompileFunctions(js::wasm::ModuleEnvironment const&, js::wasm::CompilerEnvironment const&, js::LifoAlloc&, mozilla::Vector<js::wasm::FuncCompileInput, 8ul, js::SystemAllocPolicy> const&, js::wasm::CompiledCode*, mozilla::UniquePtr<char [], JS::FreePolicy>*) js/src/wasm/WasmIonCompile.cpp:7103:12
#14 0x565483da372d in ExecuteCompileTask(js::wasm::CompileTask*, mozilla::UniquePtr<char [], JS::FreePolicy>*) js/src/wasm/WasmGenerator.cpp:664:12
#15 0x565483da398d in js::wasm::ModuleGenerator::locallyCompileCurrentTask() js/src/wasm/WasmGenerator.cpp:719:8
#16 0x565483da4795 in js::wasm::ModuleGenerator::finishFuncDefs() js/src/wasm/WasmGenerator.cpp:850:24
#17 0x565483d7b421 in bool DecodeCodeSection<js::wasm::Decoder>(js::wasm::ModuleEnvironment const&, js::wasm::Decoder&, js::wasm::ModuleGenerator&) js/src/wasm/WasmCompile.cpp:686:13
#18 0x565483d7addc in js::wasm::CompileBuffer(js::wasm::CompileArgs const&, js::wasm::ShareableBytes const&, mozilla::UniquePtr<char [], JS::FreePolicy>*, mozilla::Vector<mozilla::UniquePtr<char [], JS::FreePolicy>, 0ul, js::SystemAllocPolicy>*, JS::OptimizedEncodingListener*) js/src/wasm/WasmCompile.cpp:708:8
#19 0x565483dfa5da in js::WasmModuleObject::construct(JSContext*, unsigned int, JS::Value*) js/src/wasm/WasmJS.cpp:1713:7
#20 0x56548270ee19 in CallJSNative js/src/vm/Interpreter.cpp:459:13
#21 0x56548270ee19 in CallJSNativeConstructor js/src/vm/Interpreter.cpp:475:8
[...]
#33 0x56548237127c in main js/src/shell/js.cpp:12320:12
SUMMARY: AddressSanitizer: heap-use-after-free js/src/wasm/WasmIonCompile.cpp:2836:35 in (anonymous namespace)::FunctionCompiler::delegatePadPatches(mozilla::Vector<js::jit::MControlInstruction*, 8ul, js::SystemAllocPolicy> const&, unsigned int)
Shadow bytes around the buggy address:
0x0c187fffc330: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
=>0x0c187fffc340: fd fd fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd
0x0c187fffc350: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Heap left redzone: fa
Freed heap region: fd
==32005==ABORTING
```
|
|
1,798,798 | 16,142,211 |
Created attachment 9301665
poc.html
I found a vulnerability in firefox android where a window prompt with a long description can cover fullscreen notifications which can lead to spoofs.
steps to produce
1. open http://103.186.0.20/poc2.html or open poc.html
2. Click the open to google button
3. Then a dialog prompt window appears with a long description and covers the fullscreen notification
4 then click ok
OS: Android 10 (Samsung M31)
i attached the poc video files.
thank you
|
|
1,798,823 | 16,142,361 |
Created attachment 9301684
rsa_bug.c
Steps to reproduce:
Compile the attached file with NSS and run in one of the two modes: either supply "\x00" or "" as the RSA modulus.
Actual results:
Buffer overflow in the first case, segmentation fault in the second.
See reports from address sanitizer in the test case.
Expected results:
Checking the input size and not operating beyond the array length.
|
|
1,791,363 | 16,079,892 |
The following testcase crashes on mozilla-central revision 20220912-b66bbbcc4467 (debug build, run with --fuzzing-safe --ion-offthread-compile=off):
enqueueMark('set-color-gray');
enqueueMark(newGlobal());
enqueueMark('set-color-black');
enqueueMark(newGlobal());
gcparam("markStackLimit", 1);
gczeal(8, 1);
throw 1;
Backtrace:
received signal SIGSEGV, Segmentation fault.
#0 0x00005555576141a2 in js::GCMarker::setMarkColor(js::gc::MarkColor) ()
#1 0x0000555557616d1d in js::GCMarker::markDelayedChildren(js::gc::Arena*, js::gc::MarkColor) ()
#2 0x0000555557617269 in js::GCMarker::processDelayedMarkingList(js::gc::MarkColor, js::SliceBudget&) ()
#3 0x000055555761470f in js::GCMarker::markAllDelayedChildren(js::SliceBudget&, js::GCMarker::ShouldReportMarkTime) ()
#4 0x0000555557613e76 in js::GCMarker::markUntilBudgetExhausted(js::SliceBudget&, js::GCMarker::ShouldReportMarkTime) ()
#5 0x00005555575d182f in js::gc::GCRuntime::markUntilBudgetExhausted(js::SliceBudget&, js::GCMarker::ShouldReportMarkTime) ()
#6 0x0000555557660909 in js::gc::GCRuntime::markGray(JS::GCContext*, js::SliceBudget&) ()
#7 0x0000555557683141 in sweepaction::SweepActionSequence::run(js::gc::SweepAction::Args&) ()
#8 0x0000555557678e63 in sweepaction::SweepActionForEach<js::gc::SweepGroupsIter, JSRuntime*>::run(js::gc::SweepAction::Args&) ()
#9 0x000055555766848c in js::gc::GCRuntime::performSweepActions(js::SliceBudget&) ()
#10 0x00005555575d4d7a in js::gc::GCRuntime::incrementalSlice(js::SliceBudget&, JS::GCReason, bool) ()
#11 0x00005555575d80d4 in js::gc::GCRuntime::gcCycle(bool, js::SliceBudget const&, JS::GCReason) ()
#12 0x00005555575d9286 in js::gc::GCRuntime::collect(bool, js::SliceBudget const&, JS::GCReason) ()
#13 0x00005555575dc189 in js::gc::GCRuntime::runDebugGC() ()
#14 0x00005555575a3b17 in bool js::gc::GCRuntime::checkAllocatorState<(js::AllowGC)1>(JSContext*, js::gc::AllocKind) ()
#15 0x00005555575a5c0d in js::gc::TenuredCell* js::gc::detail::AllocateTenuredImpl<(js::AllowGC)1>(JSContext*, js::gc::AllocKind, unsigned long) ()
#16 0x00005555570a4638 in js::SharedShape::getInitialShape(JSContext*, JSClass const*, JS::Realm*, js::TaggedProto, unsigned long, js::EnumFlags<js::ObjectFlag>) ()
#17 0x0000555556f58623 in NewObject(JSContext*, JSClass const*, JS::Handle<js::TaggedProto>, js::gc::AllocKind, js::NewObjectKind) ()
#18 0x0000555556ed28ef in js::GlobalObject::createBlankPrototype(JSContext*, JS::Handle<js::GlobalObject*>, JSClass const*) ()
#19 0x0000555556ecf17c in js::GlobalObject::resolveConstructor(JSContext*, JS::Handle<js::GlobalObject*>, JSProtoKey, js::GlobalObject::IfClassIsDisabled) ()
#20 0x0000555557073c72 in js::GlobalObject::getOrCreateSavedFramePrototype(JSContext*, JS::Handle<js::GlobalObject*>) ()
#21 0x00005555570738ee in js::SavedFrame::create(JSContext*) ()
#22 0x000055555707caa5 in js::SavedStacks::createFrameFromLookup(JSContext*, JS::Handle<js::SavedFrame::Lookup>) ()
#23 0x000055555707c51e in js::SavedStacks::getOrCreateSavedFrame(JSContext*, JS::Handle<js::SavedFrame::Lookup>) ()
#24 0x0000555557079949 in js::SavedStacks::insertFrames(JSContext*, JS::MutableHandle<js::SavedFrame*>, mozilla::Variant<JS::AllFrames, JS::MaxFrames, JS::FirstSubsumedFrame>&&) ()
#25 0x0000555557078801 in js::SavedStacks::saveCurrentStack(JSContext*, JS::MutableHandle<js::SavedFrame*>, mozilla::Variant<JS::AllFrames, JS::MaxFrames, JS::FirstSubsumedFrame>&&) ()
#26 0x000055555729b645 in JS::CaptureCurrentStack(JSContext*, JS::MutableHandle<JSObject*>, mozilla::Variant<JS::AllFrames, JS::MaxFrames, JS::FirstSubsumedFrame>&&) ()
#27 0x00005555572a056e in js::CaptureStack(JSContext*, JS::MutableHandle<JSObject*>) ()
#28 0x0000555556f21c12 in JSContext::setPendingException(JS::Handle<JS::Value>, js::ShouldCaptureStack) ()
#29 0x0000555556d4c19b in js::ThrowOperation(JSContext*, JS::Handle<JS::Value>) ()
#30 0x0000555556d4307d in Interpret(JSContext*, js::RunState&) ()
[...]
#39 0x0000555556b9f654 in main ()
rax 0x555555887d51 93824995589457
rbx 0x7ffff6019328 140737320686376
rcx 0x5555582cdae8 93825039915752
rdx 0x0 0
rsi 0x7ffff7105770 140737338431344
rdi 0x7ffff7104540 140737338426688
rbp 0x7fffffffaaa0 140737488333472
rsp 0x7fffffffaa80 140737488333440
r8 0x7ffff7105770 140737338431344
r9 0x7ffff7f99800 140737353717760
r10 0x0 0
r11 0x0 0
r12 0x1 1
r13 0x2 2
r14 0x1 1
r15 0x1 1
rip 0x5555576141a2 <js::GCMarker::setMarkColor(js::gc::MarkColor)+354>
=> 0x5555576141a2 <_ZN2js8GCMarker12setMarkColorENS_2gc9MarkColorE+354>: movl $0x7f7,0x0
0x5555576141ad <_ZN2js8GCMarker12setMarkColorENS_2gc9MarkColorE+365>: callq 0x555556c349f4 <abort>
|
|
1,791,873 | 16,083,788 |
STR:
1. Make sure you are not signed in to a Firefox Account
2. Open Firefox View
3. Navigate to tab-pickup section via keyboard
4. Expand the tab pickup list section via keyboard
5. Hit "Tab" to navigate to next element
Expected:
- The "Continue" button within the "Switch seamlessly between devices" is focused
Actual:
- The "Try Colorways" (or next focusable element in the DOM) is focused instead
Considering there are alternate ways to sign into your Firefox Account, this may be a low severity issue...but it does break the tab pickup list setup flow if navigating with only keyboard/screen reader so that might tip severity in the other direction.
|
|
1,792,163 | 16,085,697 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Build ID: 20220922214429
## Steps to reproduce
0. Set `browser.privateWindowSeparation.enabled` to true
1. Open Nightly in a regular window.
2. Open a private window. (This window should have a private browsing icon on taskbar.)
3. Open Library from the private window.
4. Right click a link in Library and choose `Open in New Window`.
## Actual result
The link opens in a new private window, as indicated by the private logo on titlebar and no history is saved, yet the taskbar icon is the regular one. This new private window is also grouped with other regular windows.
## Expected result
The new private window should have a private browsing icon on taskbar. It should be grouped with other private windows, if any.
## Additional notes
1. This bug happens only when Library is opened from a private window. When it is opened from a regular window, there are `Open in New Window` and `Open in New Private Window`. Both work and group properly.
2. For Library opened from a private window, `Open` and `Open in New Tab` are also bugged if all private windows were closed.
Needinfo :bhearsum since he recently worked on bugs related to Private Window Separation.
|
|
1,785,814 | 16,036,316 |
Created attachment 9290449
rec of the issue.gif
**[Notes]:**
- This issue might affect the "Pin Private Window" modal from the MR Onboarding flow for the existing users as the modal is displayed even if the "Private Window" shortcut is already pinned to the taskbar.
**[Affected versions]:**
- Firefox Nightly 105.0a1 - Build ID: 20220612185901
**[Affected Platforms]:**
- Windows 10 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- "nimbus.debug" pref set to "true".
- "browser.promo.pin.enabled" set to "true"
- Have the "Remote Settings Devtools" add-on installed from [here](https://github.com/mozilla-extensions/remote-settings-devtools/releases).
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Click the "Remote Settings Devtools" tollbar button from the right part of the toolbar.
3. Switch the environment to "Stage" and restart the browser.
4. Navigate to the "about:studies?optin_slug=cmuresandesktop-nimbus-exploration-080522&optin_branch=treatment-a&optin_collection=nimbus-preview" URL.
5. Open a "Private Window" and click the "Pin to taskbar" button.
6. Restart the browser and navigate to the "about:telemetry" page.
7. Search for the "os.environment.is_taskbar_pinned_private" scalar and observe the value.
**[Expected result]:**
- The value of the "os.environment.is_taskbar_pinned_private" scalar is set to "true".
**[Actual result]:**
- The value of the "os.environment.is_taskbar_pinned_private" scalar is set to "false".
**[Regression window]:**
- Considering that this issue is not reproducible on Firefox Beta 104 using the Mozregression tool I have managed to find the following regression window:
Last good revision: 113593df627273c8e66f58bf735c38ad7e937f38
First bad revision: 23d27ffb8a811e38a46621aa06044ff3acaac2b9
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=113593df627273c8e66f58bf735c38ad7e937f38&tochange=23d27ffb8a811e38a46621aa06044ff3acaac2b9
From the pushlog it seems that Bug 1761291 might have caused this regression.
@Ben could you please take a look over this?
**[Additional Notes]:**
- The "os.environment.is_taskbar_pinned" is correctly recorded for the normal browsing shortcut.
- Attached a screen recording of the issue.
|
|
1,786,009 | 16,037,529 |
The attached testcase crashes on mozilla-central revision 20220818-6502583dede7 (build with (metadatabuildFlags not available)).
For detailed crash information, see attachment.
To reproduce the issue, perform the following steps:
1. Download the attached testcase, save as "test.bin".
2a. Build with `--enable-fuzzing` (requires Clang and ASan, also build gtests using `./mach gtest dontruntests`).
2b. Alternatively you can download builds from TC using `python -mfuzzfetch -a --fuzzing --target firefox gtest` (see https://github.com/MozillaSecurity/fuzzfetch).
3. Run `FUZZER=NetworkHttp2ProxyHttp2 objdir/dist/bin/firefox test.bin`
|
|
1,786,246 | 16,040,503 |
Created attachment 9290845
SkipThisStepButton.png
**[Affected versions]:**
- Firefox Nightly 105.0a1 (Build ID: 20220821185924)
**[Affected Platforms]:**
- macOS 12.5.1
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “browser.aboutwelcome.templateMR” pref set to true.
**[Steps to reproduce]:**
1. Restart the browser and navigate to the “about:welcome” page.
2. Click the “Skip this step” button until the “Import Data” screen is displayed.
3. Observe the “Skip this step” button from the bottom-right corner of the screen.
**[Expected result]:**
- The “Skip this step” button is correctly displayed and contains its label.
**[Actual result]:**
- A tiny gray button without a label is displayed.
**[Regression Window]:**
- The issue is not reproducible with older Nightly 105.0a1 builds. Considering this using mozregression tools, I have found the regression range. Here are the results:
Last good revision: 1d022fd2c07541e725479a3070e5ef4a513c5ac4
First bad revision: a5fd749503d01b1fed163a3a8d0c190f69cdd978
Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1d022fd2c07541e725479a3070e5ef4a513c5ac4&tochange=a5fd749503d01b1fed163a3a8d0c190f69cdd978)
From this pushlog it seems that Bug 1781378 may have introduced this behavior.
**[Notes]:**
- The button is actionable.
- Attached is a screenshot of the issue.
|
|
1,786,509 | 16,042,028 |
Created attachment 9291119
Screen Recording.mov
**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220822190304
**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.3.1
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “devtools.chrome.enabled” pref set to true.
- Have the Browser Console opened.(Ctrl+Shift+J)
- Have the “Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();” syntax copied to clipboard.
**[Steps to reproduce]:**
1. Focus the browser console (Ctrl+Shift+J), paste the “Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();” string, and press “Enter” key.
2. Modify the height by resizing the browser and observe the elements displayed on the browser’s page.
**[Expected result]:**
- The modals are correctly rendered and have a scroll bar when the browser is resized.
**[Actual result]:**
- The modals do not have a scroll bar when the browser is resized and a part of the elements cannot be accessed.
**[Notes]:**
- This issue is not reproducible for new users.
- Attached is a screen recording of the issue.
|
|
1,786,828 | 16,043,752 |
Created attachment 9291340
x button not working on mobile modal pbm.gif
**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220823214727
- Firefox Beta 105.0b2 - Build ID: 20220823185840
**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.3.1
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have the new Firefox profile opened.
**[Steps to reproduce]:**
1. Open a new private window and click the “Download Firefox Focus” button.
2. Click the “x” button from the “Get Firefox Focus” modal.
**[Expected result]:**
- The Close button from the “Get Firefox Focus” modal is actionable and the modal is dismissed.
**[Actual result]:**
- The Close button from the “Get Firefox Focus” modal is not actionable and the modal is not dismissed.
**[Regression window]:**
- The issue is not reproducible with older Nightly 104.0a1 builds. Considering this using mozregression tools I have found the regression range. Here are the results:
Last good revision: 43c1a6141f9ddb20447c6e5075612f59405cd9fb
First bad revision: 32f983ac16be4e76e049a2a3c98e8035433727d9
Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=43c1a6141f9ddb20447c6e5075612f59405cd9fb&tochange=32f983ac16be4e76e049a2a3c98e8035433727d9)
From this pushlog it seems that Bug 1758506 may have introduced this behavior.
**[Notes]:**
- The “Get Firefox Focus” modal can be dismissed by pressing the “Esc” key.
- The issue is not reproducible with keyboard navigation, in this case the modal is successfully dismissed.
- Attached is a screen recording of the issue.
|
|
1,786,881 | 16,043,949 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0
Steps to reproduce:
System - Ubuntu 22.04
Update Firefox Developer Edition from 104b9 version to 105b2.
Actual results:
Noticed that browser is no longer authorized in my proxy. Also with full resetting the browser or reinstall.
Firefox shows the proxy authorization window by circle but never authorizes, no matter what you type in form fields.
Roll back to 105b1 - confirmed same behavior
Roll back to 104b9 - this version has normal proxy auth
Expected results:
Correct proxy auth same as version 104b9
|
|
1,787,115 | 16,045,309 |
Created attachment 9291503
rec of the issue.gif
**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220824213405
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.7
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- "devtools.chrome.enabled" set to "true";
- Have the "Browser Console" opened.
- Have a custom theme applied from "about:addons>Themes".
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Focus the "Browser Console" and run the `Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();` code.
3. Navigate through the Onboarding modals until the "Colorways" one is displayed.
4. Click the "Skip this step" button and observe the browser's theme.
**[Expected result]:**
- The existing user theme is still enabled.
**[Actual result]:**
- The theme is changed to the system theme.
**[Additional Notes]:**
- The user set theme is also reset to the system one if the "Default" theme option from the "Colorways" modal is selected.
- Attached a screen recording of the issue.
|
|
1,787,293 | 16,046,080 |
Reddit post:
https://www.reddit.com/r/firefox/comments/wwnxtu/youtube_videos_freezing_since_updating_to_1040/
appears to be the result of recent video performance changes. A workaround exists (setting `media.wmf.zero-copy-nv12-texture` and `gfx.direct3d11.reuse-decoder-device` to `false`), but this needs to be addressed quickly.
|
|
1,787,396 | 16,046,789 |
Created attachment 9291691
SeeWhat'sNew_FirefoxView.gif
**[Affected versions]:**
- Firefox Nightly 106.0a1 (Build ID: 20220825222149)
- Firefox Beta 105.0b3 (Build ID: 20220825185816)
**[Affected Platforms]:**
- macOS 12.5.1
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “browser.aboutwelcome.templateMR” pref set to true.
- Have the “devtools.chrome.enabled” pref set to true.
- Have the “Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();” syntax copied to the clipboard.
**[Steps to reproduce]:**
1. Focus the Browser Console (Ctrl + Shift + J) and paste the syntax from prerequisites.
2. Press the “Enter” key.
3. Click the “Skip this step” button until the “MR Gratitude” modal is displayed.
4. Click the “See what’s new” button.
5. Observe what happens.
**[Expected result]:**
- The Onboarding flow ends, and the “Firefox View” page is opened in the current tab.
**[Actual result]:**
- The Onboarding flow ends, and the “Firefox View” page is not opened.
**[Regression Window]:**
- The issue is not reproducible with older Nightly 105.0a1 builds. Considering this using mozregression tools, I have found the regression range. Here are the results:
Last good revision: 5403acde30c2edaba6dac6f0890cb413e7b75c76
First bad revision: 6e8e2b449b07a8d5a02e75692a25353ac360d852
Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5403acde30c2edaba6dac6f0890cb413e7b75c76&tochange=6e8e2b449b07a8d5a02e75692a25353ac360d852)
From this pushlog it seems that Bug 1783049 may have introduced this behavior.
**[Notes]:**
- This issue is not reproducible on new users’ onboarding.
- Attached is a screen recording of the issue.
|
|
1,787,551 | 16,047,611 |
Crash report: https://crash-stats.mozilla.org/report/index/e769cfb1-341f-421d-bb63-349e90220826
Reason: ```SIGSEGV / SEGV_MAPERR```
Top 10 frames of crashing thread:
```
0 libandroid.so libandroid.so@0x000000000001eeac
1 libandroid.so libandroid.so@0x000000000001eea4
2 libandroid.so libandroid.so@0x000000000001d5b0
3 libandroid.so libandroid.so@0x000000000001d444
4 libxul.so gfxFT2FontList::FindFonts gfx/thebes/gfxFT2FontList.cpp:1460
5 libxul.so gfxPlatformFontList::InitFontList gfx/thebes/gfxPlatformFontList.cpp:576
6 libxul.so gfxPlatformFontList::Initialize gfx/thebes/gfxPlatformFontList.cpp:259
7 libxul.so gfxPlatform::Init gfx/thebes/gfxPlatform.cpp:979
8 libxul.so gfxPlatform::GetPlatform gfx/thebes/gfxPlatform.cpp:460
9 libxul.so gfxPlatform::InitializeCMS gfx/thebes/gfxPlatform.cpp:2111
```
|
|
1,787,609 | 16,048,074 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.102 Safari/537.36 Edg/104.0.1293.70
Steps to reproduce:
`getMsgHdrForMsgId()` may cause massive loss of MSF files since it potentially opens all folders in the profile hitting the limit of open files.
As we've seen in bug 1773822, opening too many folder databases leads to the loss of the MSF files which can't be opened any more and are then considered invalid and are deleted.
|
|
1,787,619 | 16,048,184 |
Created attachment 9291903
TroubleshootingInfo.txt
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0
Steps to reproduce:
* Observed the Firefox view icon at the left end of the tab bar.
* selected it, and observed a button to start using it.
* received dialog to enter primary password (I had cancelled the entry when I started nightly.)
* Tried to enter password several times, very carefully, but unsuccessfully. This may be a problem as I almost always get the password correct when I am careful.
* Tried to cancel the password dialog, hoping to cancel setting up the tab pickup feature. This did not work.
* Finally my primary password was accepted after several more attempts during which I was watching which keys I pressed.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0
Computer network name: mars
Machine type: AMD64
Processor type: Intel64 Family 6 Model 158 Stepping 9, GenuineIntel
Platform type: Windows-10-10.0.19043-SP0
Operating system: Windows
Operating system release: 10
Operating system version: 10.0.19043
Actual results:
* Entering the password seemed to fail even when entered correctly.
* Cancelling the primary password dialog did not cancel setting up the tab pickup feature.
Expected results:
* Entering the primary password should have worked as reliably as as when the dialog is presented at other times.
* Cancelling the primary password dialog should have cancelled setting up the tab pickup feature.
|
|
1,787,926 | 16,051,360 |
Created attachment 9292103
demo_site.zip
I noticed that one of my Firefox extensions stopped working after Developer Edition updated a couple of days ago. There are no errors thrown, but a script sits waiting for a Promise to resolve.
I've tried my best to boil the extension down to a small website (1 main js, 3 imports, status readout) which I've included with this report.
I've found three points - a top-level await, an `import()` function and a top-level `import` statement. Changing any one of these lines unblocks the demo's progress. I've marked these lines in the source files - one in each module in the `/js` folder.
I believe the sticking point is dynamically importing a module (`lowlevel_api.js`) which itself imports an already loaded module (`state.js`).
I can confirm that this site works in Firefox 104 and Chrome, but not in Developer Edition 105 or Nightly 106.
MozRegression points to [this range](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6c785b80bde527e19e2b0080cd35a4ea184c5e5a&tochange=c02f1a1d3cf6fa8bffb9aaa594320969f0fdbb8c) including just bug1779421, which is why I'm filing the bug in this Component.
Steps to Reproduce:
Serve the included website and open /index.html.
Expected Results:
The site displays a status message, which should progress to a "Success!" message.
Actual Results:
The site gets stuck "Waiting for ready...".
|
|
1,787,975 | 16,051,734 |
Created attachment 9292171
Screen Shot 2022-08-29 at 10.57.52 AM.png
On the initial restart after Firefox View was enabled in Nightly it took more than 10 minutes for my sync tabs to load. I updated from 8-22 Nightly to 8-29 Nightly.
There was internet connection the whole time and I did try to reload the page twice. Eventually sync tabs loaded after a long time.
I've noticed this happening again after the inital sync as well. (probably during a time triggered refresh?)
|
|
1,788,002 | 16,051,978 |
STR
1) Activate Firefox View
2) Enable session restore
3) open a few tabs
4) activate one of the tabs(tab A) other than FxV or the last one in the tablist
5) restart Fx
ER
Fx restores the session, the active tab is tab A
AR
Fx restores the session, the active tab is tab A+1
|
|
1,788,076 | 16,052,470 |
Created attachment 9292294
rec of the issue.gif
**[Notes]:**
- The "Use Firefox recommendations" option from the "about:preferences#privacy" page is selected by default.
- If the "Use Firefox recommendations" option from the "about:preferences#privacy" page is selected the "browser.privacySegmentation.enabled" pref is set to "false".
- If the "Show detailed information" option from the "about:preferences#privacy" page is selected the "browser.privacySegmentation.enabled" pref is set to "true".
- If the "Use Firefox recommendations" button from the "Privacy segmentation" Onboarding modal is clicked the "browser.privacySegmentation.enabled" pref is set to "true".
- If the "Show detailed information" button from the "Privacy segmentation" Onboarding modal is clicked the "browser.privacySegmentation.enabled" pref is set to "false".
**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220830092750
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.5
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- `browser.aboutwelcome.templateMR` set to `true`
- `devtools.chrome.enabled` set to `true`
- Have the "Browser Console" opened.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Focus the "Browser Console" and run the "Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();" string.
3. Navigate to the "Privacy segmentation" modal and click the "Use Firefox recommendations" button.
4. Navigate to the "about:preferences#privacy" page and observe the options from the "New features that enhance you browsing" section.
**[Expected result]:**
- The "Use Firefox recommendations" option is selected.
**[Actual result]:**
- The "Show detailed information" option is selected instead.
**[Additional Notes]:**
- If the "Show detailed information" button from the "Privacy segmentation" Onboarding modal is clicked the "Use Firefox recommendations" option from the "about:preferences#privacy" page is selected instead.
- Attached a screen recording of the issue.
|
|
1,788,111 | 16,052,937 |
## steps to reproduce/what did you do?
* step 1 - opened up firefox view
* step 2 - looked at the tap pick up view
## expected behavior/ what did you think will happen?
it would show a website that i looked at this AM on my phone in firefox.
## actual behavior/ what actually happened?
nothing i looked at this AM appears in tab pick up. instead it shows the confirmation page on a website for something i ordered a couple days ago - it says that the tab is from yesterday. it also shows two other things that i viewed on sunday and have not visited those sites since sunday. i do have a screenshots of the tab pick up and a screenshot of my order confirmation email.
|
|
1,788,274 | 16,054,197 |
Created attachment 9292492
Screen Shot 2022-08-31 at 9.18.19 AM.png
## steps to reproduce/what did you do?
* step 1 - Open to Firefox View
* step 2 - Observe
Within the colorways section on the right...
- the Expires outline, part of it blends in with my orange theme and looks off
- Expiration date - is it Jan 23rd or Jan 2023?
- "Try colorways" is confusing / unexpected b/c I've already tried it - my current theme is orange
- is "colorways" considered a proper noun since it's the name of this feature? the button has it lowercase
- regardless of Jan 23 or Jan 2023 - having a prominent expiration date makes me feel a sense of urgency that i immediately dismiss b/c the date is so far into the future. i'm curious about this date and why something sooner wasn't chosen.
|
|
1,814,899 | 16,265,557 |
Steps to reproduce:
The attached sample crashes the js-shell on commit a7156afbfa575f12f60b1c8bf099d547c29bcadf when executed via commandline `--fuzzing-safe --gc-zeal=10`. The crash is flaky, but running it via `rr record --chaos` for some time should yield a crash. While the crash is in line `MOZ_ASSERT(ionScript->containsReturnAddress(returnAddr));`, the instruction is `mov rax,QWORD PTR [rbx+0x30]` instead of a normal assertion failure.
```
function f0(a1) {
const v5 = [0,0,0,0,0,0,0,0];
const v10 = new SharedArrayBuffer(1000, {});
const v12 = new Int16Array();
for (const v14 in v5.join(a1)) { }
}
f0.toString = f0;
for (let v15 = 0; v15 < 100; v15++) {
f0(f0);
}
f0();
this.unscopables;
```
```
#0 js::jit::JSJitFrameIter::checkInvalidation (this=<optimized out>, ionScriptOut=0x7ffe1b63b5c0)
at js/src/jit/JSJitFrameIter.cpp:71
#1 0x00005564199cbe93 in js::jit::TraceIonJSFrame (trc=0x7ffe1b63b938, frame=...)
at js/src/jit/JitFrames.cpp:947
#2 js::jit::TraceJitActivation (trc=0x7ffe1b63b938, activation=<optimized out>)
at js/src/jit/JitFrames.cpp:1358
#3 js::jit::TraceJitActivations (cx=<optimized out>, trc=0x7ffe1b63b938) at js/src/jit/JitFrames.cpp:1400
#4 0x00005564193b6560 in js::gc::GCRuntime::traceRuntimeCommon (this=0x6d0133323788, trc=0x7ffe1b63b938,
traceOrMark=js::gc::GCRuntime::MarkRuntime) at js/src/gc/RootMarking.cpp:303
#5 0x00005564193b6300 in js::gc::GCRuntime::traceRuntimeForMajorGC (this=0x6d0133323788, trc=0x7ffe1b63b938, session=...)
at js/src/gc/RootMarking.cpp:242
#6 0x000055641931cc57 in js::gc::GCRuntime::updateRuntimePointersToRelocatedCells (this=0x6d0133323788, session=...)
at js/src/gc/Compacting.cpp:802
#7 js::gc::GCRuntime::compactPhase (this=0x6d0133323788, reason=JS::GCReason::DEBUG_GC, sliceBudget=..., session=...)
at js/src/gc/Compacting.cpp:103
#8 0x0000556419341b8c in js::gc::GCRuntime::incrementalSlice (this=0x6d0133323788, budget=..., reason=JS::GCReason::DEBUG_GC,
budgetWasIncreased=<optimized out>) at js/src/gc/GC.cpp:3696
#9 0x0000556419346109 in js::gc::GCRuntime::gcCycle (this=0x6d0133323788, nonincrementalByAPI=false, budgetArg=...,
reason=JS::GCReason::DEBUG_GC) at js/src/gc/GC.cpp:4160
#10 0x0000556419346f63 in js::gc::GCRuntime::collect (this=0x6d0133323788, nonincrementalByAPI=<optimized out>, budget=...,
reason=JS::GCReason::DEBUG_GC) at js/src/gc/GC.cpp:4348
#11 0x0000556419311542 in js::gc::GCRuntime::runDebugGC (this=0x6d0133323788) at js/src/gc/GC.cpp:4795
#12 js::gc::GCRuntime::gcIfNeededAtAllocation (this=<optimized out>, cx=<optimized out>)
at js/src/gc/Allocator.cpp:412
#13 js::gc::GCRuntime::checkAllocatorState<(js::AllowGC)1> (this=0x6d0133323788, cx=0x6d0133336600,
kind=js::gc::AllocKind::OBJECT2_BACKGROUND) at js/src/gc/Allocator.cpp:376
#14 0x000055641931095c in js::gc::detail::AllocateObject<(js::AllowGC)1> (cx=0x6d0133336600, kind=<optimized out>, nDynamicSlots=0,
heap=js::gc::TenuredHeap, clasp=0x556419f27090 <js::PropertyIteratorObject::class_>, site=0x0)
at js/src/gc/Allocator.cpp:56
#15 0x00005564188f3319 in js::gc::CellAllocator::NewCell<js::NativeObject, (js::AllowGC)1, js::gc::AllocKind&, unsigned long const&, js::gc::InitialHeap&, JSClass const*&, js::gc
::AllocSite*&> (cx=0x6d0133336600, args=<optimized out>, args=<optimized out>,
--Type <RET> for more, q to quit, c to continue without paging--
args=<optimized out>, args=<optimized out>) at js/src/gc/Allocator.h:123
#16 JSContext::newCell<js::NativeObject, (js::AllowGC)1, js::gc::AllocKind&, unsigned long const&, js::gc::InitialHeap&, JSClass const*&, js::gc::AllocSite*&> (this=0x6d013333660
0, args=<optimized out>, args=<optimized out>, args=<optimized out>, args=<optimized out>,
args=<optimized out>) at js/src/vm/JSContext.h:266
#17 js::NativeObject::create (cx=0x6d0133336600, kind=js::gc::AllocKind::OBJECT2_BACKGROUND, heap=js::gc::TenuredHeap, shape=...,
site=0x0) at js/src/vm/NativeObject-inl.h:446
#18 0x0000556418b84b50 in NewPropertyIteratorObject (cx=0x6d0133336600) at js/src/vm/Iteration.cpp:803
#19 CreatePropertyIterator (cx=0x6d0133336600, objBeingIterated=..., props=..., supportsIndices=false, indices=0x0, numShapes=0)
at js/src/vm/Iteration.cpp:845
#20 0x0000556418b7f0eb in GetIteratorImpl<false> (obj=..., cx=<optimized out>)
at js/src/vm/Iteration.cpp:1262
#21 js::GetIterator (cx=0x6d0133336600, obj=...) at js/src/vm/Iteration.cpp:1293
#22 0x0000556418b86112 in js::ValueToIterator (cx=0x6d0133336600, vp=...) at js/src/vm/Iteration.cpp:1619
```
|
|
1,814,961 | 16,265,937 |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/111.0 ID:20230129213553
With my current profile I have a couple of pages which regularly do not finish loading (see bug 1503259). All of them are trying to load fonts from eg. fonts.gstatic.com and as it looks like the response is never received.
First I thought it is related to the NoScript extension but after removing it the problem was still persistent after a while - probably when certain items from the network cache gets removed.
Here a profile: https://share.firefox.dev/3Y0WV4p
So far I don't have steps for a fresh profile but also haven't had the time yet to strip down my daily profile.
Here some pages where I can see this behavior:
* https://www.selenium.dev/blog/2023/headless-is-going-away
* https://hacks.mozilla.org/2023/02/announcing-interop-2023/
* https://www.podcasts.com/
|
|
1,815,843 | 16,273,506 |
Created attachment 9316720
screenshot
The buttons in the permissions panel are not fully visible if there are domain names that are a bit longer. It's a regression from bug 1799460.
|
|
1,815,885 | 16,273,839 |
### Steps to reproduce
1. Have a fresh install.
2. On the main device login in with a Firefox account and open a few tabs.
3. On a second device login with the same account, open a few tabs and wait for or perform a manual sync.
4. Observe the homepage on the main device.
### Expected behavior
A Tab Pickup CFR is displayed above the "See all synced tabs" section.
### Actual behavior
The Tab Pickup CFR is not displayed.
### Device information
* Firefox version: Nightly 111.0a1 (2023-02-09)
* Android device model: Google Pixel 7
* Android OS version: Android 13
### Any additional information?
|
|
1,816,074 | 16,275,026 |
Created attachment 9316978
folder f10 crash.webm
Crash report: https://crash-stats.mozilla.org/report/index/5c14a758-c6b0-416f-9b4c-019130230210
Reason: ```SIGSEGV / SEGV_MAPERR```
Top 10 frames of crashing thread:
```
0 libxul.so RefPtr<mozilla::dom::NodeInfo>::get const mfbt/RefPtr.h:286
0 libxul.so RefPtr<mozilla::dom::NodeInfo>::operator-> const mfbt/RefPtr.h:316
0 libxul.so nsINode::IsInNamespace const dom/base/nsINode.h:774
0 libxul.so nsIContent::IsXULElement const dom/base/nsIContent.h:200
0 libxul.so nsIContent::IsAnyOfXULElements<nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*, nsStaticAtom*> const dom/base/nsIContent.h:208
0 libxul.so mozilla::dom::XULButtonElement::FromNode<nsIContent> dom/xul/XULButtonElement.h:78
1 libxul.so mozilla::dom::XULButtonElement::FromNode<nsIContent> dom/xul/XULButtonElement.h:78
1 libxul.so nsXULPopupManager::MayShowMenu layout/xul/nsXULPopupManager.cpp:714
2 libxul.so mozilla::dom::XULButtonElement::OpenMenuPopup dom/xul/XULButtonElement.cpp:184
3 libxul.so nsMenuBarListener::KeyPress layout/xul/nsMenuBarListener.cpp:290
```
**Platforms**
- Affected: Ubuntu 22.04
- Unaffected: Windows and macOS
**Steps to Reproduce**
1. Launch Firefox
2. Right click on the bookmarks toolbar and select add folder
3. Press F10 on the keyboard
**Notes**
- The crash can be seen in the added attachment
- Happens on Firefox 111.0a1 and 110.0
- Feel free to change the component to the right one if this isn't the correct one.
- On Windows the menu bar is shown as expected.
|
|
1,816,138 | 16,275,377 |
Created attachment 9317066
CBH_feature_off.gif
**[Affected versions]:**
- Firefox Nightly 111.0a1 (Build ID 20230209213208)
**[Affected platforms]:**
- Windows 10 x64
- macOS 12.5
- Ubuntu 22.04.1 x64
**[Prerequisites]:**
Have the following preferences set:
- cookiebanners.service.detectOnly set to true
- cookiebanners.service.mode set to 1
- cookiebanners.ui.desktop.enabled set to true
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to a website with cookie banners (eg. cnn.com).
3. Click the "Not Now" button from the CBH doorhanger.
4. Navigate to the "about:preferences#privacy" page in a new tab.
5. Tick the "Reduce Cookie Banners" option.
6. Return to the website with the cookie banner and refresh the page.
**[Expected result]:**
- The feature is enabled and the cookie banner is blocked.
**[Actual result]:**
- The cookie banner remains displayed.
- The CBH entry from the Protections Panel is not displayed.
**[Notes]:**
- Since the "cookiebanners.service.detectOnly" preference is not toggled to false by enabling Cookie Banner Reduction via about:preferences, the feature remains disabled.
- The issue is not reproducible if the user chose to enable the feature from the doorhanger.
- Attached a screen recording of the issue:
|
|
1,816,464 | 16,278,739 |
Created attachment 9317371
CBH_unenrollment.gif
**[Affected versions]:**
- Firefox Nightly 111.0a1 (Build ID 20230212085204)
**[Affected platforms]:**
- Windows 10 x64
- macOS 12.5
- Ubuntu 22.04.1 x64
**[Prerequisites]:**
- Have a browser profile enrolled in the CBH Nimbus experiment.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to a website with cookie banners (eg. cnn.com).
3. Click on the "Reject Requests" button.
4. Navigate to the about:studies page and observe the list of studies.
**[Expected result]:**
- The cookie banner is dismissed and the client remains enrolled in the experiment.
**[Actual result]:**
- The cookie banner remains displayed and the user is unenrolled from the experiment.
**[Notes]:**
- The cause of this issue is that clicking the "Reject Requests" button will flip the "cookiebanners.service.detectOnly" preference to "false". Since this preference has its value modified by the experiment, flipping it causes the user to unenroll and all other preferences to reset to their default values.
- Unenrollment by modifying an experiment's preference is the expected behavior for Nimbus experiments
- Attached a screen recording of the issue:
|
|
1,816,917 | 16,281,791 |
See here: https://bugzilla.mozilla.org/show_bug.cgi?id=1811992#c22
|
|
1,810,518 | 16,237,675 |
Created attachment 9312432
rec of the issue.gif
**[Notes]:**
- The following validation error is displayed in the "Browser Console": [Error](https://drive.google.com/file/d/1Y_p3xLGqWYsDMP2YDqxiW5aHNQSS34sw/view?usp=share_link)
**[Affected versions]:**
- Firefox Release 100.0.2 - Build ID: 20220519220738
- Firefox Release 101.0.1 - Build ID: 20220608170832
- Firefox Release 102.0.1 - Build ID: 20220705093820
- Firefox Release 103.0.2 - Build ID: 20220808125904
**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.6.1
- Linux Mint 20.2
**[Prerequisites]:**
- Have a Firefox en-* locale installed.
- Have a Firefox profile betwen 7 and 28 days old.
- Have the "[user.js](https://drive.google.com/file/d/1Smyn7FOByDTtgFWGsdgV_dOywUfgqTXx/view?usp=share_link" file saved to disk.
**[Steps to reproduce]:**
1. Navigate to the profile folder from prerequisites and paste the "user.js" file.
2. Open the browser using the profile from the prerequisites.
3. Navigate to the "about:studies" page and observe the listed experiments.
**[Expected result]:**
- The "import-bookmarks-image-and-segmentation-en" experiment is displayed.
**[Actual result]:**
- The "import-bookmarks-image-and-segmentation-en" experiment is **NOT** displayed.
**[Additional Notes]:**
- This issue is also reproducible with the import experiments for the [DE](https://experimenter.services.mozilla.com/nimbus/import-bookmarks-image-and-segmentation-de/) and [FR](https://experimenter.services.mozilla.com/nimbus/import-bookmarks-image-and-segmentation-fr/) regions.
- This issue is no longer reproducible on Firefox 104 and above versions.
- Attached is a screen recording of the issue:
|
|
1,810,536 | 16,237,776 |
According to this [search](https://crash-stats.mozilla.org/search/?proto_signature=~neqo&address=~e5e5&product=Firefox&date=%3E%3D2022-07-12T19%3A57%3A00.000Z&date=%3C2023-01-12T19%3A57%3A00.000Z&_facets=signature&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports), we have some UAF crashes in our Http/3 code.
|
|
1,810,711 | 16,238,784 |
The following testcase triggers an assertion failure in debug builds of Spidermonkey built from current HEAD:
RegExp.sameZoneAs = RegExp;
with (this.newGlobal(RegExp)) {
function f3(a4, a5) {
async function f6(a7, a8, a9) {
return a4;
}
const v11 = ("-9").replace;
try {
v11();
} catch(e13) {
const o14 = {
};
Object.defineProperty(o14, "getPrototypeOf", { enumerable: true, value: f6 });
const v16 = new Proxy(e13, o14);
v16.stack;
}
return f3;
}
const v19 = new Promise(f3);
}
// CRASH INFO
// ==========
// TERMSIG: 11
// STDERR:
// Assertion failure: IsObjectValueInCompartment(v, compartment()), at /home/builder/firefox/js/src/vm/NativeObject.h:1083
Here is a part of the backtrace from gdb:
#0 0x0000555557525f2c in js::NativeObject::checkStoredValue (this=0x37c283201248, v=...) at js/src/vm/NativeObject.h:1083
#1 0x000055555769b65d in js::NativeObject::setSlot (this=0x37c283201248, slot=2, value=...) at js/src/vm/NativeObject.h:1091
#2 0x00005555576fba93 in js::EnvironmentObject::setAliasedBinding (this=0x37c283201248, slot=2, v=...) at js/src/vm/EnvironmentObject-inl.h:46
#3 0x00005555578cafd1 in js::EnvironmentObject::setAliasedBinding (this=0x37c283201248, bi=..., v=...) at js/src/vm/EnvironmentObject-inl.h:60
#4 0x00005555578a5971 in js::CallObject::create (cx=0x7ffff772d100, frame=...) at js/src/vm/EnvironmentObject.cpp:182
#5 0x00005555578b50d7 in js::InitFunctionEnvironmentObjects (cx=0x7ffff772d100, frame=...) at js/src/vm/EnvironmentObject.cpp:4001
#6 0x0000555557be104f in js::InterpreterFrame::initFunctionEnvironmentObjects (this=0x7ffff56fc1c8, cx=0x7ffff772d100) at js/src/vm/Stack.cpp:171
#7 0x0000555557be12ad in js::InterpreterFrame::prologue (this=0x7ffff56fc1c8, cx=0x7ffff772d100) at js/src/vm/Stack.cpp:189
#8 0x00005555576bd5ac in Interpret (cx=0x7ffff772d100, state=...) at js/src/vm/Interpreter.cpp:2131
#9 0x00005555576bd001 in js::RunScript (cx=0x7ffff772d100, state=...) at js/src/vm/Interpreter.cpp:431
#10 0x00005555576d4523 in js::InternalCallOrConstruct (cx=0x7ffff772d100, args=..., construct=js::NO_CONSTRUCT, reason=js::CallReason::Call) at js/src/vm/Interpreter.cpp:579
#11 0x00005555576d4a99 in InternalCall (cx=0x7ffff772d100, args=..., reason=js::CallReason::Call) at js/src/vm/Interpreter.cpp:614
#12 0x00005555576d4c49 in js::Call (cx=0x7ffff772d100, fval=..., thisv=..., args=..., rval=..., reason=js::CallReason::Call) at js/src/vm/Interpreter.cpp:646
#13 0x0000555557ea4287 in js::ScriptedProxyHandler::getPrototype (this=0x5555596e1a50 <js::ScriptedProxyHandler::singleton>, cx=0x7ffff772d100, proxy=..., protop=...) at js/src/proxy/ScriptedProxyHandler.cpp:250
#14 0x0000555557ea00d2 in js::Proxy::getPrototype (cx=0x7ffff772d100, proxy=..., proto=...) at js/src/proxy/Proxy.cpp:297
#15 0x00005555578e0e1d in js::GetPrototype (cx=0x7ffff772d100, obj=..., protop=...) at js/src/vm/ObjectOperations-inl.h:50
#16 0x00005555578baed1 in FindErrorInstanceOrPrototype (cx=0x7ffff772d100, obj=..., result=...) at js/src/vm/ErrorObject.cpp:626
#17 0x00005555578ba890 in js::ErrorObject::getStack_impl (cx=0x7ffff772d100, args=...) at js/src/vm/ErrorObject.cpp:664
#18 0x00005555578ba740 in JS::CallNonGenericMethod<&(IsObject(JS::Handle<JS::Value>)), &js::ErrorObject::getStack_impl> (cx=0x7ffff772d100, args=...) at obj-debug/dist/include/js/CallNonGenericMethod.h:103
#19 0x00005555578ba6ac in js::ErrorObject::getStack (cx=0x7ffff772d100, argc=0, vp=0x7fffffff49a8) at js/src/vm/ErrorObject.cpp:656
#20 0x00005555576e604c in CallJSNative (cx=0x7ffff772d100, native=0x5555578ba660 <js::ErrorObject::getStack(JSContext*, unsigned int, JS::Value*)>, reason=js::CallReason::Getter, args=...) at js/src/vm/Interpreter.cpp:459
#21 0x00005555576d4313 in js::InternalCallOrConstruct (cx=0x7ffff772d100, args=..., construct=js::NO_CONSTRUCT, reason=js::CallReason::Getter) at js/src/vm/Interpreter.cpp:547
#22 0x00005555576d4a99 in InternalCall (cx=0x7ffff772d100, args=..., reason=js::CallReason::Getter) at js/src/vm/Interpreter.cpp:614
#23 0x00005555576d4c49 in js::Call (cx=0x7ffff772d100, fval=..., thisv=..., args=..., rval=..., reason=js::CallReason::Getter) at js/src/vm/Interpreter.cpp:646
#24 0x00005555576d59d7 in js::CallGetter (cx=0x7ffff772d100, thisv=..., getter=..., rval=...) at js/src/vm/Interpreter.cpp:768
#25 0x0000555557a0f32a in CallGetter (cx=0x7ffff772d100, obj=..., receiver=..., id=..., prop=..., vp=...) at js/src/vm/NativeObject.cpp:2017
I'm not sure if this assertion failure has security implications, so I'm filing this as a security issue as a precaution.
|
|
1,811,549 | 16,244,355 |
Created attachment 9313313
Screen_Recording_20230120_122053_Firefox_Focus.mp4
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
1. Go to any webpage
2. Rotate screen
Actual results:
Gray screen
Expected results:
Rotated screen
|
|
1,811,637 | 16,244,820 |
Crash report: https://crash-stats.mozilla.org/report/index/76fdcfa7-05c8-4b27-8cb9-2cc250230120
Reason: ```SIGSEGV / SI_KERNEL```
Top 10 frames of crashing thread:
```
0 libgobject-2.0.so.0 g_type_check_instance_cast /usr/src/debug/glib2-2.74.1-2.fc37.x86_64/gobject/gtype.c:4127
1 libgtk-3.so.0 gtk_container_accessible_get_n_children /usr/src/debug/gtk3-3.24.36-1.fc37.x86_64/gtk/a11y/gtkcontaineraccessible.c:51
2 libatk-bridge-2.0.so.0 impl_get_ChildCount /usr/src/debug/at-spi2-atk-2.38.0-5.fc37.x86_64/atk-adaptor/adaptors/accessible-adaptor.c:139
3 libatk-bridge-2.0.so.0 impl_prop_GetSet /usr/src/debug/at-spi2-atk-2.38.0-5.fc37.x86_64/droute/droute.c:364
4 libatk-bridge-2.0.so.0 handle_properties /usr/src/debug/at-spi2-atk-2.38.0-5.fc37.x86_64/droute/droute.c:443
4 libatk-bridge-2.0.so.0 handle_message /usr/src/debug/at-spi2-atk-2.38.0-5.fc37.x86_64/droute/droute.c:597
5 libdbus-1.so.3 _dbus_object_tree_dispatch_and_unlock /usr/src/debug/dbus-1.14.4-1.fc37.x86_64/dbus/dbus-object-tree.c:1021
5 libdbus-1.so.3 <name omitted> /usr/src/debug/dbus-1.14.4-1.fc37.x86_64/dbus/dbus-connection.c:4742
5 libdbus-1.so.3 dbus_connection_dispatch /usr/src/debug/dbus-1.14.4-1.fc37.x86_64/dbus/dbus-connection.c:4574
6 libatspi.so.0 message_queue_dispatch /usr/src/debug/at-spi2-core-2.44.1-2.fc37.x86_64/atspi/atspi-gmain.c:89
```
This looks like a UAF inside GTK accessibility code. There are 28 crashes like that in the last week, which isn't a huge number in absolute terms, but seems like it must be a lot for Linux accessibility code.
|
|
1,812,232 | 16,250,371 |
Created attachment 9313938
geolocation_prompt.png
Steps to reproduce:
1) Open Firefox Nightly
2) Navigate to about:config
3) Set `browser.urlbar.showSearchTerms.featureGate` to `true`
4) Set `browser.urlbar.showSearchTerms.enabled` to `true`
5) Enter a search term in the address bar
6) Press enter
7) Wait for Google to request access to your location (It's not clear to me how they decide to do this, it seems like a 50/50 chance each time).
8) Alternatively, open developer tools
9) Go to 'Console'
10) Paste `document.documentElement.addEventListener("click", () => navigator.geolocation.getCurrentPosition(() => {}));`
11) Press enter
12) Click anywhere on the page content
Expected results:
Geolocation permission prompt is anchored to the permission request button (like a normal webpage) or suppressed.
Actual results:
Geolocation prompt looks like its awkwardly anchored to the magnifying glass.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.