Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
---|---|---|---|
1,757,721 | 15,797,278 |
When using a custom profile for running geckodriver the created backup file for `user.js` is never deleted. As such the backup files accumulate over time:
```
-rw-r--r-- 1 henrik staff 3672 Jan 24 13:44 user.geckodriver_backup
-rw-r--r-- 1 henrik staff 3799 Mar 2 11:37 user.geckodriver_backup_1
-rw-r--r-- 1 henrik staff 3799 Mar 2 11:37 user.geckodriver_backup_2
-rw-r--r-- 1 henrik staff 3799 Mar 2 11:38 user.geckodriver_backup_3
-rw-r--r-- 1 henrik staff 3799 Mar 2 11:38 user.js
```
Creating a back-up of that file is a new feature in geckodriver 0.30.0 and was introduced by bug 1705770.
It's probably not blocking the 0.31.0 release but might be easy to fix.
|
|
1,745,874 | 15,696,264 |
Created attachment 9255182
poc.html
Tested Version: Ubuntu 64-bit memory 8G + linux64-fuzzing-asan-opt(95.0.1 (64-bit)) => linux64-fuzzing-asan-opt
Loading poc.html into the firefox browser to create a new tab(Using the grizzly tool(allow pop-ups)),This poc is not 100% stable, and I can only trigger it in the docker container,if it fails, please repeat more times. the crash report is as follows:
=================================================================
==40332==ERROR: AddressSanitizer: heap-use-after-free on address 0x6180000503f8 at pc 0x7f9161f84be0 bp 0x7f913ee81570 sp 0x7f913ee81568
READ of size 8 at 0x6180000503f8 thread T33 (MediaDe~hine #1)
#0 0x7f9161f84bdf in mozilla::AudioSink::NotifyAudioNeeded() /builds/worker/checkouts/gecko/dom/media/mediasink/AudioSink.cpp:361:10
#1 0x7f9161fa63af in operator() /builds/worker/workspace/obj-build/dist/include/MediaEventSource.h:404:7
#2 0x7f9161fa63af in ApplyWithArgsImpl<(lambda at /builds/worker/workspace/obj-build/dist/include/MediaEventSource.h:403:37)> /builds/worker/workspace/obj-build/dist/include/MediaEventSource.h:214:5
#3 0x7f9161fa63af in mozilla::detail::ListenerImpl<mozilla::AbstractThread, std::enable_if<TakeArgs<void (mozilla::AudioSink::*)(RefPtr<mozilla::AudioData> const&)>::value, mozilla::MediaEventListener>::type mozilla::MediaEventSourceImpl<(mozilla::ListenerPolicy)1, RefPtr<mozilla::AudioData> >::ConnectInternal<mozilla::AbstractThread, mozilla::AudioSink, void (mozilla::AudioSink::*)(RefPtr<mozilla::AudioData> const&)>(mozilla::AbstractThread*, mozilla::AudioSink*, void (mozilla::AudioSink::*)(RefPtr<mozilla::AudioData> const&))::'lambda'(RefPtr<mozilla::AudioData>&&), RefPtr<mozilla::AudioData> >::ApplyWithArgs(RefPtr<mozilla::AudioData>&&) /builds/worker/workspace/obj-build/dist/include/MediaEventSource.h:236:5
#4 0x7f9161b8caee in applyImpl<mozilla::detail::Listener<RefPtr<mozilla::AudioData> >, void (mozilla::detail::Listener<RefPtr<mozilla::AudioData> >::*)(RefPtr<mozilla::AudioData> &&), StoreCopyPassByRRef<RefPtr<mozilla::AudioData> > , 0UL> /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:1147:12
#5 0x7f9161b8caee in apply<mozilla::detail::Listener<RefPtr<mozilla::AudioData> >, void (mozilla::detail::Listener<RefPtr<mozilla::AudioData> >::*)(RefPtr<mozilla::AudioData> &&)> /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:1153:12
#6 0x7f9161b8caee in mozilla::detail::RunnableMethodImpl<mozilla::detail::Listener<RefPtr<mozilla::AudioData> >*, void (mozilla::detail::Listener<RefPtr<mozilla::AudioData> >::*)(RefPtr<mozilla::AudioData>&&), true, (mozilla::RunnableKind)0, RefPtr<mozilla::AudioData>&&>::Run() /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:1200:13
#7 0x7f915ba95b70 in mozilla::AutoTaskDispatcher::TaskGroupRunnable::Run() /builds/worker/workspace/obj-build/dist/include/mozilla/TaskDispatcher.h:227:35
#8 0x7f915baa2f0d in mozilla::TaskQueue::Runner::Run() /builds/worker/checkouts/gecko/xpcom/threads/TaskQueue.cpp:208:20
#9 0x7f915bacac3b in nsThreadPool::Run() /builds/worker/checkouts/gecko/xpcom/threads/nsThreadPool.cpp:305:14
#10 0x7f915babd9f4 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1169:16
#11 0x7f915bac76ec in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:467:10
#12 0x7f915cf4ee0d in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:300:20
#13 0x7f915cdd91f1 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#14 0x7f915cdd91f1 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#15 0x7f915cdd91f1 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#16 0x7f915bab6d7b in nsThread::ThreadFunc(void*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:391:10
#17 0x7f917722a09e in _pt_root /builds/worker/checkouts/gecko/nsprpub/pr/src/pthreads/ptthread.c:201:5
#18 0x7f9178b50608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
#19 0x7f9178718292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
0x6180000503f8 is located 888 bytes inside of 896-byte region [0x618000050080,0x618000050400)
freed by thread T33 (MediaDe~hine #1) here:
#0 0x563dfcba4cb2 in __interceptor_free /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:111:3
#1 0x7f9161f88e9e in operator() /builds/worker/workspace/obj-build/dist/include/mozilla/UniquePtr.h:463:5
#2 0x7f9161f88e9e in reset /builds/worker/workspace/obj-build/dist/include/mozilla/UniquePtr.h:305:7
#3 0x7f9161f88e9e in ~UniquePtr /builds/worker/workspace/obj-build/dist/include/mozilla/UniquePtr.h:253:18
#4 0x7f9161f88e9e in mozilla::AudioSinkWrapper::~AudioSinkWrapper() /builds/worker/checkouts/gecko/dom/media/mediasink/AudioSinkWrapper.cpp:17:37
#5 0x7f9161f88fdd in mozilla::AudioSinkWrapper::~AudioSinkWrapper() /builds/worker/checkouts/gecko/dom/media/mediasink/AudioSinkWrapper.cpp:17:37
#6 0x7f915c92d09f in mozilla::MozPromise<bool, nsresult, false>::ThenValueBase::ResolveOrRejectRunnable::Run() /builds/worker/workspace/obj-build/dist/include/mozilla/MozPromise.h:487:21
#7 0x7f915ba95b70 in mozilla::AutoTaskDispatcher::TaskGroupRunnable::Run() /builds/worker/workspace/obj-build/dist/include/mozilla/TaskDispatcher.h:227:35
#8 0x7f915baa2f0d in mozilla::TaskQueue::Runner::Run() /builds/worker/checkouts/gecko/xpcom/threads/TaskQueue.cpp:208:20
#9 0x7f915bacac3b in nsThreadPool::Run() /builds/worker/checkouts/gecko/xpcom/threads/nsThreadPool.cpp:305:14
#10 0x7f915babd9f4 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1169:16
#11 0x7f915bac76ec in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:467:10
#12 0x7f915cf4ee0d in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:300:20
#13 0x7f915cdd91f1 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#14 0x7f915cdd91f1 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#15 0x7f915cdd91f1 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#16 0x7f915bab6d7b in nsThread::ThreadFunc(void*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:391:10
#17 0x7f917722a09e in _pt_root /builds/worker/checkouts/gecko/nsprpub/pr/src/pthreads/ptthread.c:201:5
#18 0x7f9178b50608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
previously allocated by thread T33 (MediaDe~hine #1) here:
#0 0x563dfcba4f1d in __interceptor_malloc /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3
#1 0x563dfcbdfb8d in moz_xmalloc /builds/worker/checkouts/gecko/memory/mozalloc/mozalloc.cpp:52:15
#2 0x7f9161bc2a7d in operator new /builds/worker/workspace/obj-build/dist/include/mozilla/cxxalloc.h:33:10
#3 0x7f9161bc2a7d in operator() /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:2871:9
#4 0x7f9161bc2a7d in mozilla::AudioSinkWrapper::CreatorImpl<mozilla::MediaDecoderStateMachine::CreateAudioSink()::$_31>::Create(mozilla::media::TimeUnit const&) /builds/worker/checkouts/gecko/dom/media/mediasink/AudioSinkWrapper.h:42:14
#5 0x7f9161f89bd2 in mozilla::AudioSinkWrapper::Start(mozilla::media::TimeUnit const&, mozilla::MediaInfo const&) /builds/worker/checkouts/gecko/dom/media/mediasink/AudioSinkWrapper.cpp:174:30
#6 0x7f9161f9b01f in mozilla::VideoSink::Start(mozilla::media::TimeUnit const&, mozilla::MediaInfo const&) /builds/worker/checkouts/gecko/dom/media/mediasink/VideoSink.cpp:219:29
#7 0x7f9161a322be in mozilla::MediaDecoderStateMachine::StartMediaSink() /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:3460:29
#8 0x7f9161a1c504 in mozilla::MediaDecoderStateMachine::MaybeStartPlayback() /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:3052:3
#9 0x7f9161a3a864 in mozilla::MediaDecoderStateMachine::ResumeMediaSink() /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:3930:3
#10 0x7f9161bdcedd in applyImpl<mozilla::MediaDecoderStateMachine, void (mozilla::MediaDecoderStateMachine::*)()> /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:1147:12
#11 0x7f9161bdcedd in apply<mozilla::MediaDecoderStateMachine, void (mozilla::MediaDecoderStateMachine::*)()> /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:1153:12
#12 0x7f9161bdcedd in mozilla::detail::RunnableMethodImpl<mozilla::MediaDecoderStateMachine*, void (mozilla::MediaDecoderStateMachine::*)(), true, (mozilla::RunnableKind)0>::Run() /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:1200:13
#13 0x7f915ba95b70 in mozilla::AutoTaskDispatcher::TaskGroupRunnable::Run() /builds/worker/workspace/obj-build/dist/include/mozilla/TaskDispatcher.h:227:35
#14 0x7f915baa2f0d in mozilla::TaskQueue::Runner::Run() /builds/worker/checkouts/gecko/xpcom/threads/TaskQueue.cpp:208:20
#15 0x7f915bacac3b in nsThreadPool::Run() /builds/worker/checkouts/gecko/xpcom/threads/nsThreadPool.cpp:305:14
#16 0x7f915babd9f4 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1169:16
#17 0x7f915bac76ec in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:467:10
#18 0x7f915cf4ee0d in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:300:20
#19 0x7f915cdd91f1 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#20 0x7f915cdd91f1 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#21 0x7f915cdd91f1 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#22 0x7f915bab6d7b in nsThread::ThreadFunc(void*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:391:10
#23 0x7f917722a09e in _pt_root /builds/worker/checkouts/gecko/nsprpub/pr/src/pthreads/ptthread.c:201:5
#24 0x7f9178b50608 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
Thread T33 (MediaDe~hine #1) created by T0 (Web Content) here:
#0 0x563dfcb8f61c in __interceptor_pthread_create /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cpp:207:3
#1 0x7f917721a124 in _PR_CreateThread /builds/worker/checkouts/gecko/nsprpub/pr/src/pthreads/ptthread.c:458:14
#2 0x7f917720b3ce in PR_CreateThread /builds/worker/checkouts/gecko/nsprpub/pr/src/pthreads/ptthread.c:533:12
#3 0x7f915bab9bcd in nsThread::Init(nsTSubstring<char> const&) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:607:18
#4 0x7f915bac59cf in nsThreadManager::NewNamedThread(nsTSubstring<char> const&, unsigned int, nsIThread**) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadManager.cpp:581:12
#5 0x7f915bacfc31 in NS_NewNamedThread(nsTSubstring<char> const&, nsIThread**, already_AddRefed<nsIRunnable>, unsigned int) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:163:57
#6 0x7f915bac9859 in NS_NewNamedThread /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:155:10
#7 0x7f915bac9859 in nsThreadPool::PutEvent(already_AddRefed<nsIRunnable>, unsigned int) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadPool.cpp:120:17
#8 0x7f915bacbae9 in nsThreadPool::Dispatch(already_AddRefed<nsIRunnable>, unsigned int) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadPool.cpp:357:5
#9 0x7f915baa0d23 in mozilla::TaskQueue::DispatchLocked(nsCOMPtr<nsIRunnable>&, unsigned int, mozilla::AbstractThread::DispatchReason) /builds/worker/checkouts/gecko/xpcom/threads/TaskQueue.cpp:68:26
#10 0x7f915bad3933 in mozilla::TaskQueue::Dispatch(already_AddRefed<nsIRunnable>, mozilla::AbstractThread::DispatchReason) /builds/worker/workspace/obj-build/dist/include/mozilla/TaskQueue.h:87:14
#11 0x7f915ba95755 in mozilla::AutoTaskDispatcher::DispatchTaskGroup(mozilla::UniquePtr<mozilla::AutoTaskDispatcher::PerThreadTaskGroup, mozilla::DefaultDelete<mozilla::AutoTaskDispatcher::PerThreadTaskGroup> >) /builds/worker/workspace/obj-build/dist/include/mozilla/TaskDispatcher.h:275:20
#12 0x7f915ba94b36 in mozilla::AutoTaskDispatcher::~AutoTaskDispatcher() /builds/worker/workspace/obj-build/dist/include/mozilla/TaskDispatcher.h:121:7
#13 0x7f915ba96ad9 in reset /builds/worker/workspace/obj-build/dist/include/mozilla/Maybe.h:639:19
#14 0x7f915ba96ad9 in mozilla::XPCOMThreadWrapper::MaybeFireTailDispatcher() /builds/worker/checkouts/gecko/xpcom/threads/AbstractThread.cpp:195:23
#15 0x7f915ba92fac in AfterProcessNextEvent /builds/worker/checkouts/gecko/xpcom/threads/AbstractThread.cpp:133:5
#16 0x7f915ba92fac in non-virtual thunk to mozilla::XPCOMThreadWrapper::AfterProcessNextEvent(nsIThreadInternal*, bool) /builds/worker/checkouts/gecko/xpcom/threads/AbstractThread.cpp
#17 0x7f915babd537 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1199:3
#18 0x7f915bac76ec in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:467:10
#19 0x7f915cf4d84f in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:85:21
#20 0x7f915cdd91f1 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#21 0x7f915cdd91f1 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#22 0x7f915cdd91f1 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#23 0x7f91635d3567 in nsBaseAppShell::Run() /builds/worker/checkouts/gecko/widget/nsBaseAppShell.cpp:137:27
#24 0x7f916772a5df in XRE_RunAppShell() /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:917:20
#25 0x7f915cdd91f1 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#26 0x7f915cdd91f1 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#27 0x7f915cdd91f1 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#28 0x7f9167729851 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:749:34
#29 0x563dfcbd987d in content_process_main(mozilla::Bootstrap*, int, char**) /builds/worker/checkouts/gecko/browser/app/../../ipc/contentproc/plugin-container.cpp:57:28
#30 0x563dfcbd9ca8 in main /builds/worker/checkouts/gecko/browser/app/nsBrowserApp.cpp:327:18
#31 0x7f917861d0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
SUMMARY: AddressSanitizer: heap-use-after-free /builds/worker/checkouts/gecko/dom/media/mediasink/AudioSink.cpp:361:10 in mozilla::AudioSink::NotifyAudioNeeded()
Shadow bytes around the buggy address:
0x0c3080002020: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3080002030: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3080002040: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3080002050: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3080002060: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x0c3080002070: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd[fd]
0x0c3080002080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c3080002090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c30800020a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c30800020b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c30800020c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==40332==ABORTING
This vuln is discovered by bo13oy of Cyber Kunlun Lab.
Thanks.
|
|
1,746,696 | 15,702,230 |
Fx96 needs UTM params updated as per feedback from DS
|
|
1,747,741 | 15,712,613 |
Created attachment 9256924
gc.js
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
Steps to reproduce:
See the attached test file, gc.js .
With records and tuples enabled, this test runs a loop 1000 times in which a closure with a reference to a tuple is allocated.
Actual results:
mach record-tuple jstests Tuple/gc
## non262/Tuple/gc.js: rc = -11, run time = 0.101771
Assertion failure: this->flags() == 0, at /home/tjc/gecko-fork/js/src/gc/Cell.h:785
REGRESSION - non262/Tuple/gc.js
[0|1|0|0] 100% ==========================================================>| 0.2s
REGRESSIONS
non262/Tuple/gc.js
FAIL
Expected results:
The test should pass. I have a patch coming shortly.
|
|
1,743,273 | 15,673,606 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36 Edg/96.0.1054.34
Steps to reproduce:
After launching Firefox in various scenarios, 'gfx.font_rendering.cleartype_params.rendering_mode' does not have any effect.
Various scenarios: Launching normally, troubleshoot mode, refresh Firefox, new installation on a new Windows user profile.
Actual results:
I prefer to use 'gfx.font_rendering.cleartype_params.rendering_mode=5'. At first launch, this option does not affect font rendering. Fonts look like they are rendering with the default value of '-1'.
about:config shows the value '5' but rendered font look like the affecting value is '-1'. To get the desired fonts, I need to revert the value to the default and, change it back to 5.
As soon as the value changes to 5, everything becomes normal. But it stops working randomly after opening a link in a new tab. Sometimes it starts working after a refresh, sometimes it needs to be changed manually to work again.
I'm not quite sure, but this has been happening since 91 (I think).
Expected results:
At launch, fonts should be rendered with whatever the set value of 'gfx.font_rendering.cleartype_params.rendering_mode' is, instead of its default -1.
Also, after changing its value manually, it shouldn't stop affecting fonts after opening a new tab or refreshing the page.
|
|
1,743,607 | 15,677,635 |
[D131625](https://phabricator.services.mozilla.com/D131625) added indirect stubs, but caused some wasm tests failures on mips64 platform. And it seems to be caused be the following code:
```c++
#if defined(JS_CODEGEN_MIPS64)
masm.as_jr(ra);
#elif defined(JS_CODEGEN_ARM64)
```
Since MIPS64 have delay slots, we should append a `nop` to the jump instruction, otherwise the next instruction will be accidently executed.
|
|
1,744,525 | 15,685,006 |
Testcase found while fuzzing mozilla-central rev 422c7594bf65 (built with: --enable-address-sanitizer --enable-fuzzing).
This testcase only reproduces on linux with `xvfb`. As this is the standard method for running our fuzz tests, bugs like these have a significant impact on overall fuzzing performance. Please prioritize accordingly.
Testcase can be reproduced using the following commands:
```
$ pip install fuzzfetch grizzly-framework
$ python -m fuzzfetch --build 422c7594bf65 --asan --fuzzing -n firefox
$ python -m grizzly.replay ./firefox/firefox testcase.html --xvfb
```
```
[@ <missing>]
=================================================================
==703078==ERROR: AddressSanitizer: SEGV on unknown address 0x7fb06a395320 (pc 0x7fb16aeac299 bp 0x7fff739b75d0 sp 0x7fff739b72e0 T0)
==703078==The signal is caused by a READ memory access.
#0 0x7fb16aeac299 (<unknown module>)
#1 0x7fb1800c57ab (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so+0x7857ab)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (<unknown module>)
==703078==ABORTING
```
|
|
1,745,398 | 15,691,397 |
#### Affected Versions:
Nightly 97.0a1
#### Tested on:
MacOS 10.15
Windows 10
#### Steps to reproduce:
1. Launch the latest Firefox Nightly.
2. Open the hamburger menu and click the full screen button from the zoom section.
#### Expected Results:
The full screen mode is turned on.
#### Actual Results:
The full screen mode doesn't work.
#### Note:
The full screen mode is working accordingly using the keyboard shortcut.
#### Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6068f735f2247e6877eef093757cbb0fa59910e0&tochange=c8850d1e2ae3438f1fc0ec05e2faea3e8e7b9c1d
|
|
1,745,626 | 15,692,852 |
Created attachment 9254931
20211212_092112.mp4
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
open https://svelte.dev/docs#tick
Actual results:
after page loaded, load indicator still show as loading
Expected results:
it should show favicon after page loaded
|
|
1,758,800 | 15,806,592 |
From github: https://github.com/mozilla-mobile/fenix/issues/24145.
> ### Steps to reproduce
>
> 1. Download, unpack, and open the test page in the browser: [bug-select-change.zip](https://github.com/mozilla-mobile/fenix/files/8207107/bug-select-change.zip)
> 2. Click on the `select`.
>
>
> ### Expected behaviour
>
> `...`, `Value 1`, and `Value 2` should shown when the `select` is clicked.
>
> ### Actual behaviour
>
> Only `...` is shown when the `select` is clicked.
>
> ### Device name
>
> ASUS ZenFone 8
>
> ### Android version
>
> Android 11
>
> ### Firefox release type
>
> Firefox Nightly
>
> ### Firefox version
>
> 99.0a1
>
> ### Device logs
>
> _No response_
>
> ### Additional information
>
> _No response_
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,759,207 | 15,809,394 |
**Description**
When a default engine is removed by RS configuration update due contractual or other circumstances an infobar is expected to inform the user about the change. There are two ways to trigger this once the RS update is in the pipeline: restart or 5' idle. In case of f a Firefox set default search engine removal, restart won't trigger the infobar (5' idle time will)
**Affected versions**
* Firefox 98
* Beta 99
* Nightly 100
**Affected platforms**
* all
**Steps to reproduce**
1. Create a profile for a region/localization that has google.com as Firefox set default engine.
2. Have a search-config update that contains a removal of a Firefox set engine, e.g. google.com
3. Have the search-config update in pipeline. (changes are brought from RS, but not yet applied)
4. Restart browser. (RS changes are applied)
**Expected result**
Default engine is removed and Infobar is displayed stating that the google.com engine is replaced.
**Actual result**
Default engine is removed, but no Infobar is displayed in this case
**Regression range**
* Not a regression
**Note:**
This issue does not apply to user set default engine, but it applies to distribution set engines.
|
|
1,759,680 | 15,814,369 |
Created attachment 9267827
rec of the issue.gif
**[Affected versions]:**
- Firefox Release 98.0.1 - Build ID: 20220313140707
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
**[Prerequisites]:**
- Have a new Fireofox profile with the following prefs in the "about:config" page:
- "nimbus.debug" set to "true";
- Firefox is not pinned to the taskbar/dock.
- Have the "Dark" theme enabled from `about:addons>Themes>Dark`.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=welcome-back-casual-eco2203&optin_branch=treatment-b&optin_collection=nimbus-preview".
3. Restart the browser and observe the "Heart" animation.
**[Expected result]:**
- There animation is correctly displayed and rendered.
**[Actual result]:**
- The "Heart" animation has white edges.
**[Additional Notes]:**
- Attached a screen recording of the issue:
|
|
1,760,589 | 15,822,929 |
Created attachment 9268654
magnifyingGlassSearchIcon.gif
**[Affected versions]:**
- Firefox Nightly 100.0a1 (Build ID: 20220320213921)
**[Affected Platforms]:**
- macOS 11.6
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “browser.search.region” pref set to “US”.
**[Steps to reproduce]:**
1. Restart the browser and open a new private window. (Ctrl+Shift+P)
2. Click the “Download Firefox Focus” button.
3. Observe the magnifying glass Search icon from the left side of the Address Bar.
**[Expected result]:**
- The magnifying glass Search icon is correctly displayed.
**[Actual result]:**
- The magnifying glass Search icon is changed to a file icon.
**[Notes]:**
- This issue is still reproducible after a page refresh.
- This issue is reproducible with all the Search engines.
- This issue is no longer reproducible when opening a new private tab.
- Attached is a screen recording of the issue.
|
|
1,760,944 | 15,826,382 |
Steps to reproduce:
In a non-vanilla version of spidermonkey, I discovered an assertion violation. This bug is filed as the modification to spidermonkey is probably not the root-cause but instead exposes an underlying issue affecting the vanilla engine as well.
When disabling the array shift optimizations in `NativeObject::{tryShiftDenseElements,tryUnshiftDenseElements}` by letting these two function immediately return false, one of the jit-tests (js/src/jit-test/tests/basic/shifted-elements6.js) crashes in `js::jit::AssertValidObjectPtr`.
The crash happens in a small percentage of executions only, hence reproducing the issue might require some repetition.
As @iain pointed out: reproducing the issue in rr is possible if the rr flag --chaos is used.
|
|
1,761,249 | 15,828,495 |
Created attachment 9269217
marketplaceButtons_outline.png
**[Affected versions]:**
- Firefox Nightly 100.0a1 (Build ID: 20220323214810)
**[Affected Platforms]:**
- macOS 11.6
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “browser.search.region” pref set to “US”.
- Have the Dark theme of the browser enabled.
**[Steps to reproduce]:**
1. Restart the browser and open a new private window. (Ctrl+Shift+P)
2. Click the “Download Firefox Focus” button.
3. Observe the marketplace buttons.
**[Expected result]:**
- The marketplace buttons are correctly displayed and visible.
**[Actual result]:**
- The bottom part of the buttons is not visible.
**[Notes]:**
- Attached is a screenshot of the issue.
|
|
1,761,251 | 15,828,499 |
Created attachment 9269218
noCloseTooltip.gif
**[Affected versions]:**
- Firefox Nightly 100.0a1 (Build ID: 20220323214810)
**[Affected Platforms]:**
- macOS 11.6
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “browser.search.region” pref set to “US”.
**[Steps to reproduce]:**
1. Restart the browser and open a new private window. (Ctrl+Shift+P)
2. Click the “Download Firefox Focus” button.
3. Hover the “x” button from the top-right corner of the modal.
4. Observe what happens.
**[Expected result]:**
- A “Close” tooltip is displayed.
**[Actual result]:**
- No tooltip is shown.
**[Notes]:**
- Attached is a screen recording of the issue.
|
|
1,761,483 | 15,830,036 |
Testcase found while fuzzing mozilla-central rev b94d53ba65d2 (built with: --enable-address-sanitizer --enable-fuzzing).
Testcase can be reproduced using the following commands:
```
$ pip install fuzzfetch grizzly-framework
$ python -m fuzzfetch --build b94d53ba65d2 --asan --fuzzing -n firefox
$ python -m grizzly.replay ./firefox/firefox testcase.zip
```
```
[@ mozilla::dom::ReadableByteStreamControllerFillReadRequestFromQueue]
=================================================================
==503909==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000038 (pc 0x7f51c0fa1990 bp 0x7f51a4e67d50 sp 0x7f51a4e67b20 T14)
==503909==The signal is caused by a READ memory access.
==503909==Hint: address points to the zero page.
#0 0x7f51c0fa1990 in mozilla::dom::ReadableByteStreamControllerFillReadRequestFromQueue(JSContext*, mozilla::dom::ReadableByteStreamController*, mozilla::dom::ReadRequest*, mozilla::ErrorResult&) /dom/streams/ReadableByteStreamController.cpp:693:41
#1 0x7f51c0fa44c9 in mozilla::dom::ReadableByteStreamController::PullSteps(JSContext*, mozilla::dom::ReadRequest*, mozilla::ErrorResult&) /dom/streams/ReadableByteStreamController.cpp:1038:5
#2 0x7f51c0fbe37d in mozilla::dom::ReadableStreamDefaultReaderRead(JSContext*, mozilla::dom::ReadableStreamGenericReader*, mozilla::dom::ReadRequest*, mozilla::ErrorResult&) /dom/streams/ReadableStreamDefaultReader.cpp:232:19
#3 0x7f51c0fc1aba in mozilla::dom::PipeToPump::Read(JSContext*) /dom/streams/ReadableStreamPipeTo.cpp:698:3
#4 0x7f51c0fd3cee in mozilla::dom::PipeToPumpHandler::ResolvedCallback(JSContext*, JS::Handle<JS::Value>, mozilla::ErrorResult&) /dom/streams/ReadableStreamPipeTo.cpp:147:7
#5 0x7f51c0922160 in mozilla::dom::(anonymous namespace)::PromiseNativeHandlerShim::ResolvedCallback(JSContext*, JS::Handle<JS::Value>, mozilla::ErrorResult&) /dom/promise/Promise.cpp:407:12
#6 0x7f51c09228f8 in mozilla::dom::NativeHandlerCallback(JSContext*, unsigned int, JS::Value*) /dom/promise/Promise.cpp
#7 0x7f51c620fb64 in CallJSNative /js/src/vm/Interpreter.cpp:425:13
#8 0x7f51c620fb64 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) /js/src/vm/Interpreter.cpp:512:12
#9 0x7f51c6211deb in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>, js::CallReason) /js/src/vm/Interpreter.cpp:589:8
#10 0x7f51c6655bba in Call /js/src/vm/Interpreter.h:106:10
#11 0x7f51c6655bba in PromiseReactionJob(JSContext*, unsigned int, JS::Value*) /js/src/builtin/Promise.cpp:2067:10
#12 0x7f51c620fb64 in CallJSNative /js/src/vm/Interpreter.cpp:425:13
#13 0x7f51c620fb64 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) /js/src/vm/Interpreter.cpp:512:12
#14 0x7f51c6211deb in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>, js::CallReason) /js/src/vm/Interpreter.cpp:589:8
#15 0x7f51c63ccf4d in JS::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::HandleValueArray const&, JS::MutableHandle<JS::Value>) /js/src/vm/CallAndConstruct.cpp:117:10
#16 0x7f51bca422ac in mozilla::dom::PromiseJobCallback::Call(mozilla::dom::BindingCallContext&, JS::Handle<JS::Value>, mozilla::ErrorResult&) /builds/worker/workspace/obj-build/dom/bindings/PromiseBinding.cpp:35:8
#17 0x7f51b8b22737 in Call /builds/worker/workspace/obj-build/dist/include/mozilla/dom/PromiseBinding.h:89:12
#18 0x7f51b8b22737 in Call /builds/worker/workspace/obj-build/dist/include/mozilla/dom/PromiseBinding.h:102:12
#19 0x7f51b8b22737 in mozilla::PromiseJobRunnable::Run(mozilla::AutoSlowOperation&) /xpcom/base/CycleCollectedJSContext.cpp:213:18
#20 0x7f51b8b01977 in mozilla::CycleCollectedJSContext::PerformMicroTaskCheckPoint(bool) /xpcom/base/CycleCollectedJSContext.cpp:674:17
#21 0x7f51bbc08039 in LeaveMicroTask /builds/worker/workspace/obj-build/dist/include/mozilla/CycleCollectedJSContext.h:243:7
#22 0x7f51bbc08039 in ~nsAutoMicroTask /builds/worker/workspace/obj-build/dist/include/mozilla/CycleCollectedJSContext.h:395:13
#23 0x7f51bbc08039 in mozilla::dom::BodyStream::OnInputStreamReady(nsIAsyncInputStream*) /dom/base/BodyStream.cpp:671:1
#24 0x7f51b8c398fd in mozilla::NonBlockingAsyncInputStream::RunAsyncWaitCallback(mozilla::NonBlockingAsyncInputStream::AsyncWaitRunnable*, already_AddRefed<nsIInputStreamCallback>) /xpcom/io/NonBlockingAsyncInputStream.cpp:398:13
#25 0x7f51b8c3826e in mozilla::NonBlockingAsyncInputStream::AsyncWaitRunnable::Run() /xpcom/io/NonBlockingAsyncInputStream.cpp:33:14
#26 0x7f51c086ee69 in mozilla::dom::(anonymous namespace)::ExternalRunnableWrapper::WorkerRun(JSContext*, mozilla::dom::WorkerPrivate*) /dom/workers/WorkerPrivate.cpp:201:37
#27 0x7f51c085df8b in mozilla::dom::WorkerRunnable::Run() /dom/workers/WorkerRunnable.cpp:377:12
#28 0x7f51b8d45fcb in nsThread::ProcessNextEvent(bool, bool*) /xpcom/threads/nsThread.cpp:1181:16
#29 0x7f51b8d4f87c in NS_ProcessNextEvent(nsIThread*, bool) /xpcom/threads/nsThreadUtils.cpp:465:10
#30 0x7f51c0845b10 in mozilla::dom::WorkerPrivate::DoRunLoop(JSContext*) /dom/workers/WorkerPrivate.cpp:3131:7
#31 0x7f51c080bc4d in mozilla::dom::workerinternals::(anonymous namespace)::WorkerThreadPrimaryRunnable::Run() /dom/workers/RuntimeService.cpp:2165:42
#32 0x7f51b8d45fcb in nsThread::ProcessNextEvent(bool, bool*) /xpcom/threads/nsThread.cpp:1181:16
#33 0x7f51b8d4f87c in NS_ProcessNextEvent(nsIThread*, bool) /xpcom/threads/nsThreadUtils.cpp:465:10
#34 0x7f51ba45082d in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /ipc/glue/MessagePump.cpp:300:20
#35 0x7f51ba2caca1 in RunInternal /ipc/chromium/src/base/message_loop.cc:380:10
#36 0x7f51ba2caca1 in RunHandler /ipc/chromium/src/base/message_loop.cc:373:3
#37 0x7f51ba2caca1 in MessageLoop::Run() /ipc/chromium/src/base/message_loop.cc:355:3
#38 0x7f51b8d3dbe9 in nsThread::ThreadFunc(void*) /xpcom/threads/nsThread.cpp:385:10
#39 0x7f51dbcaf02e in _pt_root /nsprpub/pr/src/pthreads/ptthread.c:201:5
#40 0x7f51dddc6608 in start_thread /build/glibc-sMfBJT/glibc-2.31/nptl/pthread_create.c:477:8
#41 0x7f51dd98d162 in __clone /build/glibc-sMfBJT/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /dom/streams/ReadableByteStreamController.cpp:693:41 in mozilla::dom::ReadableByteStreamControllerFillReadRequestFromQueue(JSContext*, mozilla::dom::ReadableByteStreamController*, mozilla::dom::ReadRequest*, mozilla::ErrorResult&)
Thread T14 (DOM Worker) created by T0 (Isolated Servic) here:
#0 0x5589c163623c in __interceptor_pthread_create /builds/worker/fetches/llvm-project/compiler-rt/lib/asan/asan_interceptors.cpp:207:3
#1 0x7f51dbc9f0b4 in _PR_CreateThread /nsprpub/pr/src/pthreads/ptthread.c:458:14
#2 0x7f51dbc9035e in PR_CreateThread /nsprpub/pr/src/pthreads/ptthread.c:533:12
#3 0x7f51b8d40f05 in nsThread::Init(nsTSubstring<char> const&) /xpcom/threads/nsThread.cpp:611:18
#4 0x7f51c086c5b2 in mozilla::dom::WorkerThread::Create(mozilla::dom::WorkerThreadFriendKey const&) /dom/workers/WorkerThread.cpp:102:7
#5 0x7f51c07ebca8 in mozilla::dom::workerinternals::RuntimeService::ScheduleWorker(mozilla::dom::WorkerPrivate&) /dom/workers/RuntimeService.cpp:1324:14
#6 0x7f51c07ea9a8 in mozilla::dom::workerinternals::RuntimeService::RegisterWorker(mozilla::dom::WorkerPrivate&) /dom/workers/RuntimeService.cpp:1191:19
#7 0x7f51c0840114 in mozilla::dom::WorkerPrivate::Constructor(JSContext*, nsTSubstring<char16_t> const&, bool, mozilla::dom::WorkerKind, nsTSubstring<char16_t> const&, nsTSubstring<char> const&, mozilla::dom::WorkerLoadInfo*, mozilla::ErrorResult&, nsTString<char16_t>) /dom/workers/WorkerPrivate.cpp:2524:24
#8 0x7f51c087c4d3 in mozilla::dom::RemoteWorkerChild::ExecWorkerOnMainThread(mozilla::dom::RemoteWorkerData&&) /dom/workers/remoteworkers/RemoteWorkerChild.cpp:449:41
#9 0x7f51c08b3dda in operator() /dom/workers/remoteworkers/RemoteWorkerChild.cpp:306:29
#10 0x7f51c08b3dda in mozilla::detail::RunnableFunction<mozilla::dom::RemoteWorkerChild::ExecWorker(mozilla::dom::RemoteWorkerData const&)::$_2>::Run() /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:531:5
#11 0x7f51b8d121df in mozilla::SchedulerGroup::Runnable::Run() /xpcom/threads/SchedulerGroup.cpp:140:20
#12 0x7f51b8d5eef2 in mozilla::RunnableTask::Run() /xpcom/threads/TaskController.cpp:467:16
#13 0x7f51b8d2528d in mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /xpcom/threads/TaskController.cpp:778:26
#14 0x7f51b8d227a8 in mozilla::TaskController::ExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /xpcom/threads/TaskController.cpp:612:15
#15 0x7f51b8d22eb9 in mozilla::TaskController::ProcessPendingMTTask(bool) /xpcom/threads/TaskController.cpp:390:36
#16 0x7f51b8d6b881 in operator() /xpcom/threads/TaskController.cpp:124:37
#17 0x7f51b8d6b881 in mozilla::detail::RunnableFunction<mozilla::TaskController::InitializeInternal()::$_0>::Run() /builds/worker/workspace/obj-build/dist/include/nsThreadUtils.h:531:5
#18 0x7f51b8d45797 in nsThread::ProcessNextEvent(bool, bool*) /xpcom/threads/nsThread.cpp:1187:16
#19 0x7f51b8d4f87c in NS_ProcessNextEvent(nsIThread*, bool) /xpcom/threads/nsThreadUtils.cpp:465:10
#20 0x7f51ba44f17f in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /ipc/glue/MessagePump.cpp:85:21
#21 0x7f51ba2caca1 in RunInternal /ipc/chromium/src/base/message_loop.cc:380:10
#22 0x7f51ba2caca1 in RunHandler /ipc/chromium/src/base/message_loop.cc:373:3
#23 0x7f51ba2caca1 in MessageLoop::Run() /ipc/chromium/src/base/message_loop.cc:355:3
#24 0x7f51c1100d17 in nsBaseAppShell::Run() /widget/nsBaseAppShell.cpp:137:27
#25 0x7f51c5f26f7f in XRE_RunAppShell() /toolkit/xre/nsEmbedFunctions.cpp:870:20
#26 0x7f51ba2caca1 in RunInternal /ipc/chromium/src/base/message_loop.cc:380:10
#27 0x7f51ba2caca1 in RunHandler /ipc/chromium/src/base/message_loop.cc:373:3
#28 0x7f51ba2caca1 in MessageLoop::Run() /ipc/chromium/src/base/message_loop.cc:355:3
#29 0x7f51c5f261a3 in XRE_InitChildProcess(int, char**, XREChildData const*) /toolkit/xre/nsEmbedFunctions.cpp:729:34
#30 0x5589c168047d in content_process_main(mozilla::Bootstrap*, int, char**) /browser/app/../../ipc/contentproc/plugin-container.cpp:57:28
#31 0x5589c16808b0 in main /browser/app/nsBrowserApp.cpp:327:18
#32 0x7f51dd8920b2 in __libc_start_main /build/glibc-sMfBJT/glibc-2.31/csu/../csu/libc-start.c:308:16
==503909==ABORTING
```
|
|
1,754,205 | 15,767,813 |
This means that it won't properly accumulate values across multiple calls.
Some points:
* This is probably copypasta because the other two `labeled_*` metrics (`labeled_boolean` and `labeled_string`) can only be `set` not `add`-ed to
* We'll need to patch this hole in the test coverage
|
|
1,754,802 | 15,771,491 |
Created attachment 9263318
Testcase
See test-case. Screen.width / Screen.height are swapped on Chrome but not on GeckoView. If this worked, the calculations in the related bug wouldn't be wrong.
|
|
1,754,940 | 15,772,392 |
[Tracking Requested - why for this release]:
Bug 1151941 changed to use an alternate windows station as well as an alternate desktop.
However this depends on non-native theming, so we will make the alternate winstation depend on that.
However we are working on enabling win32k lockdown (a much more important security measure) in the content process and this also depends on non-native theming.
So, we will soon make that override the non-native theming pref.
|
|
1,754,968 | 15,772,554 |
Steps to reproduce:
On git commit 9f61d854547cedbde0773b2893e4f925352be3b3 the attached sample triggers an assertion violation: Assertion failure: fromPlain->shape() == fromShape, at js/src/builtin/Object.cpp:931
Overcautiously flagging as s-s.
Bisecting the issue points to commit 6b93058e9ed4c0a82172650b848b617534fc8519 related to bug 1750558.
obj-x86_64-pc-linux-gnu/dist/bin/js --baseline-warmup-threshold=10 --ion-warmup-threshold=100 --no-threads --cpu-count=1 --ion-offthread-compile=off --fuzzing-safe --differential-testing bug_shape_assert.js
bug_shape_assert.js:
```
function main() {
for (let v19 = 32; v19 < 100; v19++) { }
const v22 = [];
const v26 = {a:0,b:0};
const v28 = Object();
Object.setPrototypeOf(v22,v28);
v28.__proto__ = v26;
const v33 = Object.assign(v28,v26);
}
main();
```
|
|
1,755,320 | 15,776,558 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.80 Safari/537.36
Steps to reproduce:
- Enable ETP
- Load a google advert
- Attempt to update the targeting using https://developers.google.com/publisher-tag/reference#googletag.Slot_updateTargetingFromMap, passing an object
(diagnosis: the shim assumes a https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map argument, but the real GPT expects a plain javascript object)
Actual results:
TypeError: map.entries is not a function
Expected results:
Targeting should have updated, no error thrown
|
|
1,755,621 | 15,779,099 |
Hello,
Please let me know if you'd like me to provide more information to have this report considered in the high-quality tier.
Cheers
# WinWebAuthnManager::Register stack-buffer overflow
## Root cause analysis
The issue can be seen in the `WinWebAuthnManager::Register` function; in the below lines:
```c++
void WinWebAuthnManager::Register(
PWebAuthnTransactionParent* aTransactionParent,
const uint64_t& aTransactionId, const WebAuthnMakeCredentialInfo& aInfo) {
// ...
WEBAUTHN_EXTENSION rgExtension[1] = {};
// ...
for (const WebAuthnExtension& ext : extra.Extensions()) {
MOZ_ASSERT(cExtensions <
(int)(sizeof(rgExtension) / sizeof(rgExtension[0])));
if (ext.type() == WebAuthnExtension::TWebAuthnExtensionHmacSecret) {
HmacCreateSecret =
ext.get_WebAuthnExtensionHmacSecret().hmacCreateSecret() == true;
if (HmacCreateSecret) {
rgExtension[cExtensions].pwszExtensionIdentifier =
WEBAUTHN_EXTENSIONS_IDENTIFIER_HMAC_SECRET;
rgExtension[cExtensions].cbExtension = sizeof(BOOL);
rgExtension[cExtensions].pvExtension = &HmacCreateSecret;
cExtensions++;
}
}
```
A compromised renderer process is able to provide more than 1 extension which makes the above code corrupt adjacent stack memory. I don't believe it is possible to reach this state with plain Javascript.
Here is what a crash looks like when hitting the stack guard page (when sending a lot of extensions):
```
0:007> g
(1920.298c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
xul!mozilla::dom::WinWebAuthnManager::Register+0x30d:
00007ffc`bd4b7d9d 4c898cd4f0010000 mov qword ptr [rsp+rdx*8+1F0h],r9 ss:0000009d`48300000=????????????????
0:007> kp
# Child-SP RetAddr Call Site
00 0000009d`482fe4c0 00007ffc`bd4b7a6d xul!mozilla::dom::WinWebAuthnManager::Register(class mozilla::dom::PWebAuthnTransactionParent * aTransactionParent = <Value unavailable error>, unsigned int64 * aTransactionId = 0x0000009d`482fe778, class mozilla::dom::WebAuthnMakeCredentialInfo * aInfo = <Value unavailable error>)+0x30d [c:\mozilla-source\mozilla-unified\dom\webauthn\WinWebAuthnManager.cpp @ 301]
01 0000009d`482fe710 00007ffc`bb7f1f88 xul!mozilla::dom::WebAuthnTransactionParent::RecvRequestRegister(unsigned int64 * aTransactionId = <Value unavailable error>, class mozilla::dom::WebAuthnMakeCredentialInfo * aTransactionInfo = <Value unavailable error>)+0x1d [c:\mozilla-source\mozilla-unified\dom\webauthn\WebAuthnTransactionParent.cpp @ 27]
02 0000009d`482fe740 0000009d`482fe680 xul!mozilla::dom::PWebAuthnTransactionParent::OnMessageReceived(class IPC::Message * msg__ = 0x0000009d`482fe680)+0x1c8 [c:\mozilla-source\mozilla-unified\obj-x86_64-pc-mingw32\ipc\ipdl\PWebAuthnTransactionParent.cpp @ 257]
```
## Reproduction information
I've verified that the issue is present in the latest available tree; here's where my tree is synchronized to:
```
$ hg log
changeset: 679353:0fae6a6b254a
bookmark: autoland
tag: tip
user: Jamie Nicol <[email protected]>
date: Tue Feb 15 20:26:12 2022 +0000
summary: Bug 1755375 - Don't generate crash reports when android kills the GPU process. r=agi
```
The bug only affects Windows and doesn't need any specific hardware to reproduce.
## Reproducing the issue
1. Apply the following diff to a recent Firefox checkout:
```diff
$ hg diff
diff --git a/dom/webauthn/WebAuthnManager.cpp b/dom/webauthn/WebAuthnManager.cpp
--- a/dom/webauthn/WebAuthnManager.cpp
+++ b/dom/webauthn/WebAuthnManager.cpp
@@ -367,16 +367,19 @@ already_AddRefed<Promise> WebAuthnManage
if (!MaybeCreateBackgroundActor()) {
promise->MaybeReject(NS_ERROR_DOM_OPERATION_ERR);
return promise.forget();
}
// TODO: Add extension list building
nsTArray<WebAuthnExtension> extensions;
+ for (size_t i = 0; i < 288; i++) {
+ extensions.AppendElement(WebAuthnExtensionHmacSecret(true));
+ }
// <https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#sctn-hmac-secret-extension>
if (aOptions.mExtensions.mHmacCreateSecret.WasPassed()) {
bool hmacCreateSecret = aOptions.mExtensions.mHmacCreateSecret.Value();
if (hmacCreateSecret) {
extensions.AppendElement(WebAuthnExtensionHmacSecret(hmacCreateSecret));
}
}
```
1. Rebuild and run the browser under a debugger or attach a debugger to the browser process (`windbgx -p <pid>`)
```
$ ./mach run --debug
```
1. Run a local HTTP server to server `trigger.html`
```
$ python3 -m http.server
```
1. Visit `http://localhost:8000/trigger.html`
1. The browser process should have crashed with something similar than below:
```
0:007> g
(1920.298c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
xul!mozilla::dom::WinWebAuthnManager::Register+0x30d:
00007ffc`bd4b7d9d 4c898cd4f0010000 mov qword ptr [rsp+rdx*8+1F0h],r9 ss:0000009d`48300000=????????????????
0:007> kp
# Child-SP RetAddr Call Site
00 0000009d`482fe4c0 00007ffc`bd4b7a6d xul!mozilla::dom::WinWebAuthnManager::Register(class mozilla::dom::PWebAuthnTransactionParent * aTransactionParent = <Value unavailable error>, unsigned int64 * aTransactionId = 0x0000009d`482fe778, class mozilla::dom::WebAuthnMakeCredentialInfo * aInfo = <Value unavailable error>)+0x30d [c:\mozilla-source\mozilla-unified\dom\webauthn\WinWebAuthnManager.cpp @ 301]
01 0000009d`482fe710 00007ffc`bb7f1f88 xul!mozilla::dom::WebAuthnTransactionParent::RecvRequestRegister(unsigned int64 * aTransactionId = <Value unavailable error>, class mozilla::dom::WebAuthnMakeCredentialInfo * aTransactionInfo = <Value unavailable error>)+0x1d [c:\mozilla-source\mozilla-unified\dom\webauthn\WebAuthnTransactionParent.cpp @ 27]
02 0000009d`482fe740 0000009d`482fe680 xul!mozilla::dom::PWebAuthnTransactionParent::OnMessageReceived(class IPC::Message * msg__ = 0x0000009d`482fe680)+0x1c8 [c:\mozilla-source\mozilla-unified\obj-x86_64-pc-mingw32\ipc\ipdl\PWebAuthnTransactionParent.cpp @ 257]
```
## Exploitability
Although it is a stack overflow it doesn't seem very exploitable at first sight. I haven't really tried but the attacker doesn't control the data being overflown. You might be able to corrupt local from parent frames and do something interesting.
|
|
1,755,806 | 15,780,437 |
Created attachment 9264281
9.html
Steps to reproduce:
Tested on the latest ASAN build.
```
==93156==ERROR: AddressSanitizer: SEGV on unknown address 0x000041414141 (pc 0x7fb2dd019510 bp 0x61e000030c98 sp 0x7fff13b3a4a8 T0)
==93156==The signal is caused by a READ memory access.
#0 0x7fb2dd019510 (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xc10510)
#1 0x7fb2dd01b2ee (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xc122ee)
#2 0x7fb2dd01bd77 (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xc12d77)
#3 0x7fb2dd01cd30 (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xc13d30)
#4 0x7fb2dd370f3f (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xf67f3f)
#5 0x7fb2dd02b2cc (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xc222cc)
#6 0x7fb2f618002d in mozilla::gl::GLContext::raw_fDrawElementsInstanced(unsigned int, int, unsigned int, void const*, int) /builds/worker/checkouts/gecko/gfx/gl/GLContext.h:2521:5
#7 0x7fb2f6172d0d in mozilla::gl::GLContext::fDrawElementsInstanced(unsigned int, int, unsigned int, void const*, int) /builds/worker/checkouts/gecko/gfx/gl/GLContext.h:2504:5
#8 0x7fb2f617274c in mozilla::WebGLContext::DrawElementsInstanced(unsigned int, int, unsigned int, long, int) /builds/worker/checkouts/gecko/dom/canvas/WebGLContextDraw.cpp:918:17
#9 0x7fb2f60737c3 in DrawElementsInstanced /builds/worker/checkouts/gecko/dom/canvas/HostWebGLContext.h:743:15
#10 0x7fb2f60737c3 in void mozilla::ClientWebGLContext::Run<void (mozilla::HostWebGLContext::*)(unsigned int, int, unsigned int, long, int) const, &(mozilla::HostWebGLContext::DrawElementsInstanced(unsigned int, int, unsigned int, long, int) const), unsigned int&, int&, unsigned int&, long&, int&>(unsigned int&, int&, unsigned int&, long&, int&) const /builds/worker/checkouts/gecko/dom/canvas/ClientWebGLContext.cpp:344:12
#11 0x7fb2f60734f1 in mozilla::ClientWebGLContext::DrawElementsInstanced(unsigned int, int, unsigned int, long, int, mozilla::FuncScopeId) /builds/worker/checkouts/gecko/dom/canvas/ClientWebGLContext.cpp:4671:3
#12 0x7fb2f559f76c in mozilla::ClientWebGLContext::DrawRangeElements(unsigned int, unsigned int, unsigned int, int, unsigned int, long) /builds/worker/checkouts/gecko/dom/canvas/ClientWebGLContext.h:2046:5
#13 0x7fb2f559f2d5 in mozilla::dom::WebGL2RenderingContext_Binding::drawRangeElements(JSContext*, JS::Handle<JSObject*>, void*, JSJitMethodCallArgs const&) /builds/worker/workspace/obj-build/dom/bindings/WebGL2RenderingContextBinding.cpp:7413:24
#14 0x7fb2f5e9b9ed in bool mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>(JSContext*, unsigned int, JS::Value*) /builds/worker/checkouts/gecko/dom/bindings/BindingUtils.cpp:3306:13
#15 0x7fb2fcdb5784 in CallJSNative /builds/worker/checkouts/gecko/js/src/vm/Interpreter.cpp:425:13
#16 0x7fb2fcdb5784 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) /builds/worker/checkouts/gecko/js/src/vm/Interpreter.cpp:512:12
#17 0x7fb2fcda1cee in CallFromStack /builds/worker/checkouts/gecko/js/src/vm/Interpreter.cpp:576:10
#18 0x7fb2fcda1cee in Interpret(JSContext*, js::RunState&) /builds/worker/checkouts/gecko/js/src/vm/Interpreter.cpp:3309:16
#19 0x7fb2fcd86b01 in js::RunScript(JSContext*, js::RunState&) /builds/worker/checkouts/gecko/js/src/vm/Interpreter.cpp:394:13
#20 0x7fb2fcdb9823 in js::ExecuteKernel(JSContext*, JS::Handle<JSScript*>, JS::Handle<JSObject*>, JS::Handle<JS::Value>, js::AbstractFramePtr, JS::MutableHandle<JS::Value>) /builds/worker/checkouts/gecko/js/src/vm/Interpreter.cpp:767:13
#21 0x7fb2fd01262b in ExecuteScript(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSScript*>, JS::MutableHandle<JS::Value>) /builds/worker/checkouts/gecko/js/src/vm/CompilationAndEvaluation.cpp:515:10
#22 0x7fb2fd012935 in JS_ExecuteScript(JSContext*, JS::Handle<JSScript*>) /builds/worker/checkouts/gecko/js/src/vm/CompilationAndEvaluation.cpp:539:10
#23 0x7fb2f4301dda in mozilla::dom::JSExecutionContext::ExecScript() /builds/worker/checkouts/gecko/dom/base/JSExecutionContext.cpp:296:8
#24 0x7fb2f83f0e22 in ExecuteCompiledScript /builds/worker/checkouts/gecko/dom/script/ScriptLoader.cpp:2311:16
#25 0x7fb2f83f0e22 in mozilla::dom::ScriptLoader::EvaluateScript(nsIGlobalObject*, mozilla::dom::ScriptLoadRequest*) /builds/worker/checkouts/gecko/dom/script/ScriptLoader.cpp:2499:10
#26 0x7fb2f83eef81 in mozilla::dom::ScriptLoader::EvaluateScriptElement(mozilla::dom::ScriptLoadRequest*) /builds/worker/checkouts/gecko/dom/script/ScriptLoader.cpp:2371:10
#27 0x7fb2f83ea0a6 in mozilla::dom::ScriptLoader::ProcessRequest(mozilla::dom::ScriptLoadRequest*) /builds/worker/checkouts/gecko/dom/script/ScriptLoader.cpp:2046:10
#28 0x7fb2f83e770f in mozilla::dom::ScriptLoader::ProcessInlineScript(nsIScriptElement*, mozilla::dom::ScriptKind) /builds/worker/checkouts/gecko/dom/script/ScriptLoader.cpp:1499:10
#29 0x7fb2f83d183e in mozilla::dom::ScriptLoader::ProcessScriptElement(nsIScriptElement*) /builds/worker/checkouts/gecko/dom/script/ScriptLoader.cpp:1214:10
#30 0x7fb2f83d09ca in mozilla::dom::ScriptElement::MaybeProcessScript() /builds/worker/checkouts/gecko/dom/script/ScriptElement.cpp:118:18
#31 0x7fb2f34c22ae in nsIScriptElement::AttemptToExecute() /builds/worker/workspace/obj-build/dist/include/nsIScriptElement.h:211:18
#32 0x7fb2f34c1378 in nsHtml5TreeOpExecutor::RunScript(nsIContent*) /builds/worker/checkouts/gecko/parser/html/nsHtml5TreeOpExecutor.cpp:897:22
#33 0x7fb2f34bff89 in nsHtml5TreeOpExecutor::RunFlushLoop() /builds/worker/checkouts/gecko/parser/html/nsHtml5TreeOpExecutor.cpp:690:7
#34 0x7fb2f34c7377 in nsHtml5ExecutorFlusher::Run() /builds/worker/checkouts/gecko/parser/html/nsHtml5StreamParser.cpp:173:18
#35 0x7fb2f142488f in mozilla::SchedulerGroup::Runnable::Run() /builds/worker/checkouts/gecko/xpcom/threads/SchedulerGroup.cpp:140:20
#36 0x7fb2f1471432 in mozilla::RunnableTask::Run() /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:467:16
#37 0x7fb2f143745d in mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:770:26
#38 0x7fb2f1434d18 in mozilla::TaskController::ExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:606:15
#39 0x7fb2f1435429 in mozilla::TaskController::ProcessPendingMTTask(bool) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:390:36
#40 0x7fb2f1479bf1 in operator() /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:124:37
#41 0x7fb2f1479bf1 in mozilla::detail::RunnableFunction<mozilla::TaskController::InitializeInternal()::$_0>::Run() /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.h:531:5
#42 0x7fb2f14576c7 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1171:16
#43 0x7fb2f1462b7c in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:467:10
#44 0x7fb2f26110b8 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:85:21
#45 0x7fb2f2518f81 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#46 0x7fb2f2518f81 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#47 0x7fb2f2518f81 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#48 0x7fb2f87c70c7 in nsBaseAppShell::Run() /builds/worker/checkouts/gecko/widget/nsBaseAppShell.cpp:137:27
#49 0x7fb2fcb7d26f in XRE_RunAppShell() /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:878:20
#50 0x7fb2f2518f81 in RunInternal /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:331:10
#51 0x7fb2f2518f81 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:324:3
#52 0x7fb2f2518f81 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:306:3
#53 0x7fb2fcb7cc90 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:715:34
#54 0x561a7a7046bd in content_process_main(mozilla::Bootstrap*, int, char**) /builds/worker/checkouts/gecko/browser/app/../../ipc/contentproc/plugin-container.cpp:57:28
#55 0x561a7a704ae1 in main /builds/worker/checkouts/gecko/browser/app/nsBrowserApp.cpp:327:18
#56 0x7fb30c8960b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#57 0x561a7a6537ac in _start (/home/omair/Downloads/firefox-asan/firefox+0x587ac)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/lib/x86_64-linux-gnu/libnvidia-eglcore.so.510.47.03+0xc10510)
```
|
|
1,756,162 | 15,782,509 |
Created attachment 9264547
Top Pick option available in non US by default.mov
[Affected Versions]:
- Nightly 99.0a1 (Build ID: 20220218090822);
[Affected Platforms]:
- Windows 10 x64
- Ubuntu 20.04 x64
- macOS 10.15.7
[Prerequisites]:
- Have a new Firefox profile with the following pref set:
- Have the "browser.search.region" pref set to a non-US region, eg: RO.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to "about:preferences#privacy" page.
3. Scroll down to "Address Bar - FIrefox Suggest" section.
4. Observe the available options.
[Expected result]:
- The "Top Pick" option is NOT available.
[Actual result]:
- The "Top Pick" option is available and it is checked.
[Notes]:
- Attached is a screen recording of the issue.
|
|
1,751,443 | 15,742,748 |
Per bug 1749281 comment 2 We should avoid creating 0-channel device
|
|
1,752,270 | 15,750,503 |
+++ This bug was initially created as a clone of Bug #1735595 +++
Bug 1735595 landed a fix to not cache 408 responses.
Reporters indicate the problem is still happening (including with HTTP/2)
We'll use this bug to diagnose remaining issues.
https://firefox-source-docs.mozilla.org/networking/submitting_networking_bugs.html
@reporters: please take a look at the documentation above.
What would help in diagnosing these issues would be some HTTP logs when the bug happens:
https://firefox-source-docs.mozilla.org/networking/http/logging.html
|
|
1,753,075 | 15,758,259 |
Created attachment 9261730
Bad
Attach (recommended) or Link to PDF file here:
http://tenniscentersandpoint.com/wp-content/uploads/2015/01/ntrp-charts.pdf
Steps to reproduce the problem:
1. view the page. The colored squares on the left are strips of colored lines
2.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
|
|
1,753,438 | 15,760,948 |
**[Affected versions]:**
- Firefox Nightly 98.0a1 (Build ID: 20220203093047)
**[Affected Platforms]:**
- Windows 10 x64
- MacOS 11.6
- Ubuntu 20.04
**[Prerequisites]:**
- Have the Firefox browser en-US build installed and opened.
- Have the “browser.search.region” pref set to the “US” value.
**[Steps to reproduce]:**
1. Navigate to the “about:preferences” page.
2. Search for “Mozilla VPN”/”Mozilla Rally” using the “Find in Settings” search box.
3. Observe the results.
**[Expected result]:**
- The “Mozilla VPN”/”Mozilla Rally” section is displayed on the top part of the page.
**[Actual result]:**
- The “Mozilla VPN”/”Mozilla Rally” section is displayed in their default position.
**[Regression window]:**
- The issue is not reproducible with the older Nightly 98.0a1 build. Considering this using mozregression tools I have found the regression range. Here are the results:
Last good revision: 66356649d92ea75a45113ac5d9f2da83e5ef0a0d
First bad revision: da83a7c50181ba92c98e650805fdd7608397e2b0
Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=66356649d92ea75a45113ac5d9f2da83e5ef0a0d&tochange=da83a7c50181ba92c98e650805fdd7608397e2b0)
From this pushlog it seems that Bug 1746509 might introduce this behavior.
**[Notes]:**
- This issue is not reproducible when a search action is performed for other sections from the “about:preferences” page.
- Attached is a screen recording of the issue.
|
|
1,753,588 | 15,762,034 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
We have a large HTML table with about 200 rows, and 10 columns. The script is pulling a lot of data but generally takes about 3-5 seconds to load. This is on v93. Since v94 this has changed to over 1 minute. Thought it was our site until I went back to v93 on which it works.
Actual results:
I opened a thread on FireFox Support https://support.mozilla.org/en-US/questions/1364203. Was advised to use mozregrssion which I did. The results are on the thread. The help suggestion (Until it's fixed you can enter about:config in the URL bar and set "layout.css.cascade-layers.enabled" = false.) did not work although it did improve it.
|
|
1,748,464 | 15,718,379 |
Created attachment 9257505
2022-01-04_17h40_14.gif
**[Affected versions]:**
- Firefox RC 96.0 - Build ID: 20220103221059
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.1
- Linux Mint 20.2 Cinnamon
**[Prerequisites]:**
- Have the latest Firefox Release 96.0 en-* locale installed.
- Have the "browser.search.region" pref set to "US" in the "about:config" page.
- Have the "[user.js](https://drive.google.com/file/d/1ytSDC0Vw1FtxrS0yAeh6ruoZccnpq5eD/view?usp=sharing)" file saved to your PC.
- The browser is set as default.
**[Steps to reproduce]:**
1. Create a new profile but do not open it.
2. Navigate to the previously created profile folder and paste the "user.js" file from prerequisites.
3. Open the browser with the recently created profile and restart it.
4. Hover the "Dismiss" button from the right part of the "More From Mozilla" infobar.
5. Observe the behavior.
**[Expected result]:**
- A tooltip is displayed.
**[Actual result]:**
- There is no tooltip displayed.
**[Notes]:**
- This issue is also reproducible on the "Treatment B" branch of the experiment.
- Attached a screen recording of the issue.
|
|
1,748,828 | 15,721,298 |
Steps to reproduce:
In Firefox 91 esr (but other versions are also affected)
* go to "about:logins'
* Create New Login
* fill in Website address "moz-proxy://<proxy-address>:<proxy-port>"
* fill in Username and Password
* Click Save
The same thing happens when Firefox asks for Proxy Credentials and you check the checkbox to save those credentials.
See also https://github.com/mozilla-lockwise/lockwise-android/issues/1266
Actual results:
Clicking Save does not do anything. The new login is not saved.
Expected results:
The New Login should be saved.
|
|
1,748,982 | 15,722,470 |
Created attachment 9257996
HCM_MFM_Icon.png
[Affected versions]:
- Firefox Nightly 97.0a1 (Build ID: 20220106214936)
- Release Candidate 96.0 (Build ID: 20220103221059)
[Affected Platforms]:
- Windows 10 x64
- Ubuntu 20.04
[Prerequisites]:
- Have the Firefox browser installed and opened.
- Have the “browser.preferences.moreFromMozilla” pref set to the “true” value.
- Have the “browser.search.region” pref set to the “US” value.
- Have the High Contrast Mode enabled.
[Steps to reproduce]:
1. Navigate to the “about:preferences#moreFromMozilla” page.
2. Observe the More from Mozilla icon displayed on the left part of the page.
[Expected result]:
- The icon is visible.
[Actual result]:
- The icon is not visible.
[Notes]:
- This issue is reproducible only if the “Mozilla Rally” section is displayed.
- This issue is not reproducible on macOS 11.6.1.
- Attached is a screenshot of the issue.
|
|
1,749,742 | 15,729,870 |
**[Affected Versions]:**
- Firefox Beta 97.0b2 (Build ID: 20220111185943)
- Firefox Nightly 98.a1 (Build ID: 20220111093827)
**[Affected Platforms]:**
- Windows 10 x64
- Ubuntu 20.04 x64
- macOS 10.15.7
**[Prerequisites]:**
- Have Firefox Beta 97.0b2 downloaded on your computer.
- Have the "browser.search.region" set to "US".
- Have one of the [treatment user.js](https://drive.google.com/drive/folders/1R_Kl51yPO9RCiuUmCHNOCqs3FQQAU2bD?usp=sharing) on your computer.
- Make sure there is no other modal displayed when starting the browser (browser default window, onboarding for new users etc).
- Have a screen reader application opened.
**[Steps to reproduce]:**
1. Open Firefox Beta 97.0b2.
2. Navigate to the “about:support” page and paste the user.js file into the Profile folder.
3. Restart the browser.
4. Navigate to the second screen of the opt-in modal
5. Focus on one of the radio options and listen to the screen reader application.
**[Expected results]:**
- The screen reader application reads: "radio button, 1 of 2" then reads the description.
**[Actual results]:**
- The screen reader application reads: "radio button, 1 of 2" and the description is NOT it is not read.
|
|
1,749,758 | 15,729,961 |
**[Affected Versions]:**
- Firefox Beta 97.0b2 (Build ID: 20220111185943)
- Firefox Nightly 98.a1 (Build ID: 20220111093827)
**[Affected Platforms]:**
- Windows 10 x64
- Ubuntu 20.04 x64
- macOS 10.15.7
**[Prerequisites]:**
- Have Firefox Beta 97.0b2 downloaded on your computer.
- Have the "browser.search.region" set to "US".
- Have one of the [treatment user.js](https://drive.google.com/drive/folders/1R_Kl51yPO9RCiuUmCHNOCqs3FQQAU2bD?usp=sharing) on your computer.
- Make sure there is no other modal displayed when starting the browser (browser default, onboarding for new users etc).
**[Steps to reproduce]:**
1. Open Firefox Beta 97.0b2.
2. Navigate to the “about:support” page and paste the user.js file into the Profile folder.
3. Restart the browser.
4. Click the “Find out how” button from the modal.
5. Select the “Allow” option and click the “Save preferences” button.
6. Open the "about:preferences” page and verify that the 3rd toggle from the Firefox Suggest section is enabled.
7. Go back to “about:config" and set as `false` the `browser.urlbar.quicksuggest.dataCollection.enabled` preference.
8. Restart the browser.
9. Select the "about:preferences” tab and observe the 3rd toggle from the Firefox Suggest section.
**[Expected results]:**
- The 3rd toggle is disabled.
**[Actual results]:**
- The 3rd toggle is enabled.
**[Notes]:**
- [Here](https://drive.google.com/file/d/1EhLjEPQbu7jE9E0wgUHN2aRJKk8G1Q7Y/view?usp=sharing) is a screen recording of the issue (captured after opting-in the experiment).
- The behavior is reproducible only once. As seen in the video, I have set the preference to `false` again and followed the remaining steps, but the issue was no longer reproducible (the value remained set to `false` as expected.
|
|
1,749,955 | 15,731,337 |
Created attachment 9258885
studies.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0
Steps to reproduce:
I disabled `app.normandy.enabled` and the "Allow Nightly to install and run studies" checkbox in preferences is unchecked and disabled.
Actual results:
Studies are still being installed and enabled. `about:studies` lies that "No new studies will run.".
Expected results:
"No means no."
|
|
1,750,152 | 15,732,623 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
1. Go to Bing.com
2. Open Settings
3. Make changes to any settings except the ones relating to "Home Page" at the bottom. For instance, set a zip code or change language
4. Save settings
Actual results:
Go back to Open Settings in Bing - your changes have been lost. It does this whether you're logged in or not, regardless of operating system, and only in Firefox 96
Expected results:
Settings should persist within that session.
|
|
1,750,205 | 15,733,093 |
**[Affected versions]:**
- Firefox Beta 97.0b3 - Build ID: 20220113185849
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have a Firefox build installed.
- Have the following [user.js](https://drive.google.com/file/d/1jHrFA5FB6eqz3lJnIdsUT1V8VadEICtU/view?usp=sharing) file copied to your PC.
- Have the update channel set to "Release".
- Have a screen reader software (E.G. NVDA) installed and enabled.
**[Steps to reproduce]:**
1. Create a new Firefox profile but do not open it.
2. Navigate to the profile folder and copy the user.js file from the prerequisites.
3. Open the browser using the previously created profile.
4. Focus the "Find out how" button and press the "Enter" key.
5. Observe the behavior.
**[Expected result]:**
- The text from the second part of the "Firefox Suggest" modal is successfully recognized and read by the screen reader.
**[Actual result]:**
- The text from the first part f the "Firefox Suggest" modal is read instead.
**[Notes]:**
- This issue is reproducible on all the experiment branches.
- This issue seems to be intermittent on macOS using the VoiceOver screen reader
|
|
1,750,390 | 15,734,138 |
Created attachment 9259253
2022-01-14_16h41_49.gif
+++ This bug was initially created as a clone of Bug #1749692 +++
This is similar to bug 1749692 but different enough it should have its own bug. Cosmin brought it up on Slack.
STR
1. Create a new profile but don't start it
2. Copy a treatment user.js into the profile
3. Start the profile
The modal is shown on top of about:welcome, which we specifically want to avoid.
This may be possible in the real world because enrollment can happen on startup in new profiles. I doubt that enrollment in a new profile would have time to finish before Firefox decides whether to show the modal, but it's not possible to say for sure, so we should try to fix this.
|
|
1,750,623 | 15,737,026 |
We noticed some new crash reports on Sentry [nightly](https://sentry.prod.mozaws.net/operations/firefox-nightly/?query=is%3Aunresolved+Missing+sender+information.) and [beta](https://sentry.prod.mozaws.net/operations/firefox-beta/?query=is%3Aunresolved+Missing+sender+information.). At the moment, the volume is low, but it will be good to take a look.
```
java.lang.RuntimeException: Missing sender information.
at org.mozilla.geckoview.WebExtensionController.fromBundle(WebExtensionController.java:13)
at org.mozilla.geckoview.WebExtensionController.lambda$handleMessage$8(WebExtensionController.java:30)
at org.mozilla.geckoview.WebExtensionController.$r8$lambda$jXq3Vt-Q1PruGyhi0zkq0ncTw50
at org.mozilla.geckoview.WebExtensionController$$ExternalSyntheticLambda0.accept
at org.mozilla.geckoview.GeckoResult.lambda$accept$2(GeckoResult.java:1)
at org.mozilla.geckoview.GeckoResult.$r8$lambda$9zWUu4Bh604Sdx3PHhezEs2AuyE
at org.mozilla.geckoview.GeckoResult$$ExternalSyntheticLambda8.onValue
at org.mozilla.geckoview.GeckoResult.lambda$thenInternal$6(GeckoResult.java:2)
at org.mozilla.geckoview.GeckoResult.$r8$lambda$CtmBkNQN_okuE2MBIfsimJFUi6Q
at org.mozilla.geckoview.GeckoResult$$ExternalSyntheticLambda1.run
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8582)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:563)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1133)
org.mozilla.geckoview.UncaughtException: java.lang.RuntimeException: Missing sender information.
at org.mozilla.geckoview.GeckoResult.dispatchLocked(GeckoResult.java:4)
at org.mozilla.geckoview.GeckoResult.completeExceptionally(GeckoResult.java:4)
at org.mozilla.geckoview.GeckoResult.lambda$thenInternal$6(GeckoResult.java:10)
at org.mozilla.geckoview.GeckoResult.$r8$lambda$CtmBkNQN_okuE2MBIfsimJFUi6Q
at org.mozilla.geckoview.GeckoResult$$ExternalSyntheticLambda1.run
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8582)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:563)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1133)
```
|
|
1,750,688 | 15,737,499 |
This is from this [crash report](https://crash-stats.mozilla.org/report/index/4380d3ef-eadf-4655-bf12-231d60220118).
I hit this UAF crash during my daily use with socket process.
```
0 XUL mozilla::net::WebSocketChannel::DoStopSession(nsresult) netwerk/protocol/websocket/WebSocketChannel.cpp:2375 context
1 XUL mozilla::net::WebSocketConnectionParent::RecvOnError(nsresult const&) netwerk/protocol/websocket/WebSocketConnectionParent.cpp:58 cfi
2 XUL mozilla::net::PWebSocketConnectionParent::OnMessageReceived(IPC::Message const&) ipc/ipdl/PWebSocketConnectionParent.cpp:258 cfi
3 XUL mozilla::ipc::PBackgroundParent::OnMessageReceived(IPC::Message const&) ipc/ipdl/PBackgroundParent.cpp:3418 cfi
4 XUL mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) ipc/glue/MessageChannel.cpp:1964 cfi
5 XUL mozilla::ipc::MessageChannel::MessageTask::Run() ipc/glue/MessageChannel.cpp:1851 cfi
6 XUL nsThread::ProcessNextEvent(bool, bool*) xpcom/threads/nsThread.cpp:1189 cfi
7 XUL mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) ipc/glue/MessagePump.cpp:330 cfi
8 XUL MessageLoop::Run() ipc/chromium/src/base/message_loop.cc:306 cfi
```
|
|
1,766,592 | 15,874,943 |
Created attachment 9274000
rec of the issue.gif
**[Notes]:**
- This seems to be a tab preloading issue because the experiment message appears blocked on the "ASRouter" page right after it was dismissed.
**[Affected versions]:**
- Firefox Beta 100.0 - Build ID: 20220425210429
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have a Firefox en-* locale build installed.
- Have the "nimbus.debug" pref set to "true" in the "about:config" page.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to the "about:studies?optin_slug=firefox-focus-pbm-fx100&optin_branch=treatment&optin_collection=nimbus-preview" URL.
3. Open a new "Private Window" and click the "X" button from the right part of the "Focus Promo" message.
4. Open a new tab in the same "Private Window" and observe the behavior.
**[Expected result]:**
- The "Focus Promo" message is **NOT** displayed.
**[Actual result]:**
- The "Focus Promo" message is displayed.
**[Additional Notes]:**
- Attached a screen recording of the issue.
|
|
1,766,987 | 15,877,764 |
Created attachment 9274388
CalculFactureEDF.pdf
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.84 Safari/537.36 OPR/85.0.4341.75
Steps to reproduce:
I opened a local pdf file: "CalculFactureEDF.pdf"
This pdf contains javascript calculation fields, with specific numerical formatting.
This pdf was made with Acrobat DC 2022.
Actual results:
Fields formatting are not taken into account when I open the file :
Fields are just filled in with raw values !
If I change values, formatting is applied
Expected results:
Formatting should be taken into account
Formatting are taken into account when I open this file on other Internet browsers (such as Opera, Chrome, Edge) and of course if I open it with Acrobat Reader DC.
I think, to solve this issue, pdf javascript code should be started automatically once, for first display, to apply formatting
|
|
1,767,434 | 15,882,578 |
Created attachment 9274803
screencast.mp4
Library window is not scrolled and focused onto the selected bookmark when sorting is used after landing patch from bug #1471546.
[Tracking Requested - why for this release]: Regression
Regression range pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2e154dcda079ad6ca50bc5d18cbd0991386c5989&tochange=2ca189b8925dba3f28a1cefdc3e6f143ffbee290
mozillaregression-GUI points that regression is caused by:
Narrowed integration regression window from [78ae535c, 2ca189b8] (3 builds) to [2e154dcd, 2ca189b8] (2 builds) (~1 steps left)
Found commit message:
Bug 1471546 - Scroll to bookmark in bookmark library on initial selection when it's not visible r=mak
Differential Revision:
https://phabricator.services.mozilla.com/D139905
Steps to reproduce:
1. Open latest Mozilla Firefox Nighty 102.0a1 (2022-05-03) (64-bit)
2. Open Library
3. Sort bookmarks
4. Select bookmark
5. Notice that Library window is not scrolled and focused onto the selected bookmark
Observed results:
Library window is not scrolled and focused onto the selected bookmark when sorting is used.
Expected results:
Library window is scrolled and focused onto the selected bookmark when sorting is used.
|
|
1,767,606 | 15,884,138 |
Created attachment 9274950
rec of the issue (1).gif
**[Notes]:**
- This issue is **NOT** reproducible on Windows 11 x64, macOS 11.6, and Linux Mint 20.2 x64.
**[Affected versions]:**
- Firefox Release 100.0 - Build ID: 20220428192727
**[Affected Platforms]:**
- Windows 10 x64
- Windows 8.1 x64
**[Prerequisites]:**
- Have the environment set to "Stage (preview)" using the "Remote Settings Devtools" add-on.
- Have the [user.js](https://drive.google.com/file/d/1s-jq35a313yWo3-seOYI7VmlPwalIKBT/view?usp=sharing) file saved to your PC.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to the profile folder and paste the `user.js` file from the prerequisites.
3. Restart the browser.
4. Observe the spotlight.
**[Expected result]:**
- The "TCP" spotlight is successfully displayed and all the elements are visible.
**[Actual result]:**
- Scrollbars are wrongly displayed inside the default "TCP" spotlight.
**[Notes]:**
- This issue seems similar with bug 1766997. @Ed could you please take a look over this?
- Attached a screen recording of the issue.
|
|
1,768,014 | 15,886,258 |
This looks like `IsWin32kLockedDown` must be returning false even though it is locked down and then it tries to access GDI font functions and crashes.
It's low volume (9 clients in crash pings) , only seems to be on win11 and it's possible that it doesn't affect all content processes, so the browser remains usable.
This can only happen (AFAICT) if the function retrieval fails or the call fails.
We might be able to change the default in that case to what the sandbox policy says, so the code still behaves correctly.
Crash report: https://crash-stats.mozilla.org/report/index/091fa8e0-233b-4162-b151-4bf9c0220426
Reason: ```EXCEPTION_ACCESS_VIOLATION_READ```
Top 10 frames of crashing thread:
```
0 gdi32full.dll InsertCFontCache
1 gdi32full.dll plfCreateLOCALFONT
2 gdi32full.dll CreateFontIndirectExW
3 gdi32full.dll CreateFontIndirectWImpl
4 xul.dll gfxDWriteFontEntry::CopyFontTable gfx/thebes/gfxDWriteFontList.cpp:412
5 xul.dll gfxFontEntry::GetFontTable gfx/thebes/gfxFontEntry.cpp:579
6 xul.dll gfxDWriteFontEntry::ReadCMAP gfx/thebes/gfxDWriteFontList.cpp:523
7 xul.dll gfxFontEntry::TestCharacterMap gfx/thebes/gfxFontEntry.cpp:183
8 xul.dll gfxFontGroup::FindFontForChar gfx/thebes/gfxTextRun.cpp:3238
9 xul.dll gfxFontGroup::InitScriptRun<char16_t> gfx/thebes/gfxTextRun.cpp:2697
```
|
|
1,768,232 | 15,887,744 |
While working on bug 1766656 I discovered that if dynamic elements are allocated immediately after an nursery allocated object with no reserved slots then the object will report that it has fixed elements, with hasFixedElements() returning true and hasDynamicElements() consequently returning false.
This is because the elements appear in memory at the same place as they would have if the object did have fixed elements.
This is simple to arrange (see attached test) and I'm surprised we haven't encountered this before. Maybe it's uncommon to have objects with dynamic elements and no reserved slots.
I don't know exactly what the effect of this would be but it seems bad and a potential security concern.
|
|
1,768,397 | 15,888,971 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
This is probably filed somewhere, even though I can't find exactly what bug it is.
Over the last couple of weeks, browsing on Imgur.com can cause a GPU hang and crash.
Actual results:
Visit Imgur.com and browse, even click on different image/video pages. Occasionally the GPU Process will hard lock, CPU usage will climb to about 30% and will stay there. Controls will no longer be functional. I can get it to auto recover if I resize the window. Otherwise, it will stay that way for as long as it's active.
Even worse, sometimes it can take the driver instance with it, causing the OS to terminate the graphics driver runtime and recover.
Expected results:
The GPU process shouldn't hard lock and prevent nearly all interaction with the window.
|
|
1,761,842 | 15,835,085 |
Currently, tabbing through elements on the Private Browsing landing page skips the "Download Firefox Focus" button; jumping from the "close" button of the focus promo to the "learn more" info section link.
The button accessible on Mac when VoiceOver is active; but can't be found via the keyboard on Windows even though it is read out by NVDA. Adding `tabindex="0"` to the <a> element of the button should fix this.
|
|
1,761,945 | 15,835,781 |
**[Affected versions]:**
- Firefox Release Candidate 99.0 Build ID: 20220328190900
**[Affected Platforms]:**
- Windows 10 x64
- MacOS 11.6
- Ubuntu 20.04
**[Prerequisites]:**
- Have the Firefox browser en-GB build installed/extracted.
- Have a new Firefox profile created.
- Have the “browser.search.region” pref set to the “GB” value.
- Have the “nimbus.debug” pref set to true.
**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to the “about:studies?optin_slug=cross-promotion-firefox-focus-pbm-fx99&optin_branch=treatment-a&optin_collection=nimbus-preview” link to enroll in the experiment.
3. Open a new private window.
4. Click the "Download Firefox Focus" button from the Firefox Focus promo.
5. Observe the parameters from the opened URL.
**[Expected result]:**
- The ”https://www.mozilla.org/firefox/browsers/mobile/focus/?v=pb” link is opened.
**[Actual result]:**
- The private browsing query is missing and the “https://www.mozilla.org/firefox/browsers/mobile/focus/” link is opened.
**[Notes]:**
- Based on the [Mana page](https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=FPS&title=%5BCross+Promotion%5D+Firefox+Focus+on+PBM+-+Fx99), the link should contain the private browsing query.
|
|
1,761,947 | 15,835,784 |
Steps to reproduce:
During differential fuzzing, I encountered a miscomputation. The attached sample computes different values, depending on whether ion is enabled or not. Reproduces on git commit: 6f18c1b2e02a0293f31d9c068c03d578d2602810
Due to the unusual circumstances to trigger the miscomputation I'm flagging this bug as s-s, just derestrict as applicable. The bug itself is quite volatile, it manifests only if a GC happens during OSR.
The command line which triggers the bug on my machine is:
```
obj-x86_64-pc-linux-gnu/dist/bin/js --fast-warmup --no-threads --cpu-count=1 -ion-offthread-compile=off --fuzzing-safe --differential-testing --ion-scalar-replacement=on --gc-zeal=14,29 sample.js
```
However, the value 29 (parameter to gc-zeal) might need some adaption. I found it easiest (during manual reduring of the fuzzer output) to run the sample in a loop until the miscompute prints [object Object] instead of 8.
Disabling scalar replacement via `--ion-scalar-replacement=on` prevents the bug from manifesting.
sample.js:
```
function main() {
let v12 = 0;
let v25 = undefined;
let v26 = undefined;
do {
v12++;
const v21 = [8];
for (let v23 = 0; v23 < 4; v23++) {
v25 = Object(...v21);
}
} while (v12 < 8);
print(v25); // should be 8. is [object Object] if gc triggers during OSR
}
main();
```
loop.sh:
```
for i in {1..100}
do
echo $i;
obj-x86_64-pc-linux-gnu/dist/bin/js --fast-warmup --no-threads --cpu-count=1 --ion-offthread-compile=off --fuzzing-safe --differential-testing --ion-scalar-replacement=on --ion-osr=on --nursery-strings=off --ion-instruction-reordering=off --gc-zeal=14,$i diff.js;
done
```
.mozconfig (just in case)
```
CC=clang
CXX=clang++
ac_add_options --enable-application=js
ac_add_options --enable-js-fuzzilli
ac_add_options --enable-fuzzing
ac_add_options --disable-tests
ac_add_options --disable-shared-js
ac_add_options --enable-linker=lld
ac_add_options --enable-gczeal
ac_add_options --enable-optimize
ac_add_options --enable-debug
```
|
|
1,762,576 | 15,840,269 |
Steps to reproduce:
With Firefox Beta 99.0 and earlier Beta versions, we are seeing that Symantec DLP DLL injection into Firefox process is getting failed. DLLs that we use: clpbm.dll/ clpbm64.dll, prntm.dll/prntm64.dll and ffm.dll / ffm64.dll.
Actual results:
We are seeing that Symantec DLP DLL injection into Firefox process is getting failed. DLLs that we use: clpbm.dll/ clpbm64.dll, prntm.dll/prntm64.dll and ffm.dll / ffm64.dll.
|
|
1,762,947 | 15,844,484 |
Bug 1761105 started validation of features with variables listed (not just schemas), but we erroneously skip validation of the first branch because of this [`continue` statement](https://searchfox.org/mozilla-central/rev/26a1b0fce12e6dd495a954c542bb1e7bd6e0d548/toolkit/components/nimbus/lib/RemoteSettingsExperimentLoader.jsm#382)
|
|
1,763,874 | 15,851,353 |
Created attachment 9271542
compacting-gc-nested-tuples.js
+++ This bug was initially created as a clone of Bug #1747741 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
Steps to reproduce:
See the attached test file, compacting-gc-nested-tuples.js .
With records and tuples enabled, this test runs a loop 20 times in which it creates a nested tuple. It also calls `gczeal(14)` to ensure compacting GC.
Actual results:
```
$ mach jit-test record-tuple/compacting-gc-nested-tuples -g
(gdb) run
[...]
Thread 9 "JS Helper" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5d05640 (LWP 1268646)]
0x0000555557061095 in js::gc::detail::CellHasStoreBuffer (cell=0xfffe4b4b4b4b4b48) at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/HeapAPI.h:590
590 return GetCellChunkBase(cell)->storeBuffer;
(gdb) bt
#0 0x0000555557061095 in js::gc::detail::CellHasStoreBuffer (cell=0xfffe4b4b4b4b4b48)
at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/HeapAPI.h:590
#1 0x0000555557061069 in js::gc::IsInsideNursery (cell=0xfffe4b4b4b4b4b48)
at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/HeapAPI.h:599
#2 0x00005555570c4205 in js::gc::IsInsideNursery (obj=0xfffe4b4b4b4b4b48)
at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/HeapAPI.h:611
#3 0x0000555557eaa811 in js::CheckTracedThing<JSObject> (trc=0x7ffff5d049e8, thing=0xfffe4b4b4b4b4b48)
at /home/tjc/gecko-fork/js/src/gc/Marking.cpp:189
#4 0x0000555557ed37d8 in DoCallback<JS::Value>(js::GenericTracer*, JS::Value*, char const*)::{lambda(auto:1)#1}::operator()<JSObject*>(JSObject*) const (this=0x7ffff5d04728, thing=0x31499aa730a0) at /home/tjc/gecko-fork/js/src/gc/Marking.cpp:692
#5 0x0000555557ed33d7 in js::MapGCThingTyped<DoCallback<JS::Value>(js::GenericTracer*, JS::Value*, char const*)::{lambda(auto:1)#1}>(JS::Value const&, DoCallback<JS::Value>(js::GenericTracer*, JS::Value*, char const*)::{lambda(auto:1)#1}&&) (val=..., f=...)
at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/Value.h:1345
#6 0x0000555557ec3583 in DoCallback<JS::Value> (trc=0x7ffff5d049e0, thingp=0x7ffff693a270, name=0x555555930747 "objectElements")
at /home/tjc/gecko-fork/js/src/gc/Marking.cpp:691
#7 0x0000555557eb1026 in js::gc::TraceEdgeInternal<JS::Value> (trc=0x7ffff5d049e8, thingp=0x7ffff693a270,
name=0x555555930747 "objectElements") at /home/tjc/gecko-fork/js/src/gc/Marking.cpp:732
#8 0x0000555557ec373a in js::gc::TraceRangeInternal<JS::Value> (trc=0x7ffff5d049e8, len=1, vec=0x7ffff693a270,
name=0x555555930747 "objectElements") at /home/tjc/gecko-fork/js/src/gc/Marking.cpp:741
#9 0x00005555573ad47d in js::TraceRange<JS::Value> (trc=0x7ffff5d049e8, len=1, vec=0x7ffff693a270,
name=0x555555930747 "objectElements") at /home/tjc/gecko-fork/js/src/gc/Tracer.h:271
#10 0x000055555755377f in JSObject::traceChildren (this=0x31499aa74220, trc=0x7ffff5d049e8)
at /home/tjc/gecko-fork/js/src/vm/JSObject.cpp:3398
#11 0x0000555557e134f4 in UpdateCellPointers<JSObject> (trc=0x7ffff5d049e0, cell=0x31499aa74220)
at /home/tjc/gecko-fork/js/src/gc/Compacting.cpp:489
#12 0x0000555557e2ea5b in UpdateArenaPointersTyped<JSObject> (trc=0x7ffff5d049e0, arena=0x31499aa74000)
at /home/tjc/gecko-fork/js/src/gc/Compacting.cpp:495
#13 0x0000555557e2e765 in UpdateArenaPointers (trc=0x7ffff5d049e0, arena=0x31499aa74000)
at /home/tjc/gecko-fork/js/src/gc/Compacting.cpp:525
#14 0x0000555557e139c0 in UpdateArenaListSegmentPointers (gc=0x7ffff69187a8, arenas=...)
at /home/tjc/gecko-fork/js/src/gc/Compacting.cpp:549
#15 0x0000555557e66c90 in js::gc::ParallelWorker<ArenaListSegment, ArenasToUpdate>::run (this=0x7fffffff8d48, lock=...)
at /home/tjc/gecko-fork/js/src/gc/ParallelWork.h:57
#16 0x0000555557e8586e in js::GCParallelTask::runTask (this=0x7fffffff8d48, lock=...)
at /home/tjc/gecko-fork/js/src/gc/GCParallelTask.cpp:182
#17 0x0000555557e85a55 in js::GCParallelTask::runHelperThreadTask (this=0x7fffffff8d48, lock=...)
at /home/tjc/gecko-fork/js/src/gc/GCParallelTask.cpp:165
#18 0x00005555574a076f in js::GlobalHelperThreadState::runTaskLocked (this=0x7ffff690e000, task=0x7fffffff8d48, locked=...)
at /home/tjc/gecko-fork/js/src/vm/HelperThreads.cpp:2653
#19 0x00005555574a054b in js::GlobalHelperThreadState::runOneTask (this=0x7ffff690e000, lock=...)
at /home/tjc/gecko-fork/js/src/vm/HelperThreads.cpp:2622
#20 0x00005555574f2518 in js::HelperThread::threadLoop (this=0x7ffff693a140, pool=0x7ffff6937280)
at /home/tjc/gecko-fork/js/src/vm/InternalThreadPool.cpp:271
--Type <RET> for more, q to quit, c to continue without paging--
#21 0x00005555574f2372 in js::HelperThread::ThreadMain (pool=0x7ffff6937280, helper=0x7ffff693a140)
at /home/tjc/gecko-fork/js/src/vm/InternalThreadPool.cpp:214
#22 0x0000555557525382 in js::detail::ThreadTrampoline<void (&)(js::InternalThreadPool*, js::HelperThread*), js::InternalThreadPool*&, js::HelperThread*>::callMain<0ul, 1ul> (this=0x7ffff6917b30) at /home/tjc/gecko-fork/js/src/threading/Thread.h:220
#23 0x000055555752518b in js::detail::ThreadTrampoline<void (&)(js::InternalThreadPool*, js::HelperThread*), js::InternalThreadPool*&, js::HelperThread*>::Start (aPack=0x7ffff6917b30) at /home/tjc/gecko-fork/js/src/threading/Thread.h:209
#24 0x00007ffff7ad9947 in start_thread (arg=<optimized out>) at pthread_create.c:435
#25 0x00007ffff7b69a44 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
```
Expected results:
The test should pass. I have a patch coming shortly.
|
|
1,763,877 | 15,851,361 |
Created attachment 9271546
with.js
+++ This bug was initially created as a clone of Bug #1763874 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
Steps to reproduce:
See the attached test file, with.js .
With records and tuples enabled, this test runs a loop 500 times in which it calls Tuple.prototype.with().
Actual results:
```
mach jit-test record-tuple/with -g
(gdb) run
[...]
Thread 1 "js" received signal SIGSEGV, Segmentation fault.
0x000055555707428d in JS::Value::unboxGCPointer<JSObject, (JSValueTag)131068> (this=0x19785b13ff90) at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/Value.h:629
629 MOZ_ASSERT((asBits_ & js::gc::CellAlignMask) == 0,
(gdb) bt
#0 0x000055555707428d in JS::Value::unboxGCPointer<JSObject, (JSValueTag)131068> (this=0x19785b13ff90) at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/Value.h:629
#1 0x000055555705bf31 in JS::Value::toObject (this=0x19785b13ff90) at /home/tjc/gecko-fork/obj-x64-debug/dist/include/js/Value.h:844
#2 0x0000555557063093 in js::IsObjectValueInCompartment (v=..., comp=0x7ffff694e2a0) at /home/tjc/gecko-fork/js/src/vm/JSObject.h:1065
#3 0x0000555557062c55 in js::NativeObject::checkStoredValue (this=0x19785b100018, v=...) at /home/tjc/gecko-fork/js/src/vm/NativeObject.h:1067
#4 0x00005555572b4074 in js::NativeObject::copyDenseElements (this=0x19785b100018, dstStart=0, src=0x19785b13ff90, count=1) at /home/tjc/gecko-fork/js/src/vm/NativeObject-inl.h:98
#5 0x00005555577dbb66 in js::tuple_with (cx=0x7ffff692a200, argc=2, vp=0x7ffff6928140) at /home/tjc/gecko-fork/js/src/vm/TupleType.cpp:132
#6 0x0000555557221d52 in CallJSNative (cx=0x7ffff692a200, native=0x5555577db780 <js::tuple_with(JSContext*, unsigned int, JS::Value*)>, reason=js::CallReason::Call, args=...)
at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:420
#7 0x000055555720f743 in js::InternalCallOrConstruct (cx=0x7ffff692a200, args=..., construct=js::NO_CONSTRUCT, reason=js::CallReason::Call) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:507
#8 0x000055555720ff10 in InternalCall (cx=0x7ffff692a200, args=..., reason=js::CallReason::Call) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:567
#9 0x000055555720fcff in js::CallFromStack (cx=0x7ffff692a200, args=...) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:571
#10 0x000055555720305d in Interpret (cx=0x7ffff692a200, state=...) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:3293
#11 0x00005555571f7a31 in js::RunScript (cx=0x7ffff692a200, state=...) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:389
#12 0x0000555557211221 in js::ExecuteKernel (cx=0x7ffff692a200, script=..., envChainArg=..., evalInFrame=..., result=...) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:760
#13 0x0000555557211594 in js::Execute (cx=0x7ffff692a200, script=..., envChain=..., rval=...) at /home/tjc/gecko-fork/js/src/vm/Interpreter.cpp:792
#14 0x000055555742025e in ExecuteScript (cx=0x7ffff692a200, envChain=..., script=..., rval=...) at /home/tjc/gecko-fork/js/src/vm/CompilationAndEvaluation.cpp:515
#15 0x000055555742037b in JS_ExecuteScript (cx=0x7ffff692a200, scriptArg=...) at /home/tjc/gecko-fork/js/src/vm/CompilationAndEvaluation.cpp:539
#16 0x0000555557055d0d in RunFile (cx=0x7ffff692a200, filename=0x7fffffffe169 "/home/tjc/gecko-fork/js/src/jit-test/tests/record-tuple/with.js", file=0x7ffff7860020,
compileMethod=CompileUtf8::DontInflate, compileOnly=false) at /home/tjc/gecko-fork/js/src/shell/js.cpp:1065
#17 0x0000555557055662 in Process (cx=0x7ffff692a200, filename=0x7fffffffe169 "/home/tjc/gecko-fork/js/src/jit-test/tests/record-tuple/with.js", forceTTY=false, kind=FileScript)
at /home/tjc/gecko-fork/js/src/shell/js.cpp:1654
#18 0x000055555702cdd3 in ProcessArgs (cx=0x7ffff692a200, op=0x7fffffffd978) at /home/tjc/gecko-fork/js/src/shell/js.cpp:10896
#19 0x000055555701fdc6 in Shell (cx=0x7ffff692a200, op=0x7fffffffd978) at /home/tjc/gecko-fork/js/src/shell/js.cpp:11693
#20 0x000055555701ad6b in main (argc=13, argv=0x7fffffffdc48) at /home/tjc/gecko-fork/js/src/shell/js.cpp:12736
```
Expected results:
The test should pass. I have a patch coming shortly.
|
|
1,763,883 | 15,851,378 |
Created attachment 9271549
from.js
+++ This bug was initially created as a clone of Bug #1763877 +++
Steps to reproduce:
See the attached test file, from.js .
With records and tuples enabled, this test runs a loop 100 times in which it creates an array `c`, calls Tuple.from() on `c`, sets `c` to null, then explicitly invokes the GC.
Actual results:
```
mach jit-test record-tuple/from
```
Assertion failure: mallocedBuffers.has(buffer), at /home/tjc/gecko-fork/js/src/gc/Nursery.h:270
[...]
Exit code: -11
FAIl - record-tuple/from.js
```
Expected results:
The test should pass. I have a patch coming shortly. This is happening because my implementation of `TupleType::createUnchecked()` (which many self-hosted methods call to create a tuple from an array) directly sets the output tuple's elements header to the input array's elements header, which violates the GC's assumptions if the array is tenured and the tuple is in the nursery. I was hoping to avoid having to copy the array (since in many of the self-hosted methods, the array is only created in order to be passed to this method), but there doesn't seem to be a simple solution that's both memory-safe and doesn't copy.
|
|
1,777,217 | 15,964,515 |
Created attachment 9283366
noTelemetry_Dismiss.gif
**[Affected versions]:**
- Firefox Nightly 104.0a1 (Build ID: 20220628191450)
- Firefox Beta 103.0b2 (Build ID: 20220628190840)
**[Affected Platforms]:**
- Windows 10 x64.
- macOS 12.3.1
- Linux Mint 20.2
**[Prerequisites]:**
- Have the Firefox Beta 103 browser installed/extracted and opened.
- Have the following prefs in the "about:config" page set to true:
- “browser.newtabpage.activity-stream.asrouter.devtoolsEnabled”;
- “browser.ping-centre.log”
- Have the Browser Console opened.
**[Steps to reproduce]:**
1. Open a new tab and click the “Expand tools” button from the top right corner of the page.
2. Search for the “tcp-cfr-thank-you” message.
3. Click the “Show” button displayed on the right side of the message.
4. Dismiss the doorhanger by pressing the “Esc” key and focus the Browser Console.
5. Observe the displayed pings.
**[Expected result]:**
- A “DISMISS” event is displayed.
**[Actual result]:**
- No telemetry probe is displayed for the “DISMISS” action.
**[Notes]:**
- This issue is also reproducible if the doorhanger is dismissed by clicking outside of it.
- Attached is a screen recording of the issue.
|
|
1,777,661 | 15,967,388 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0
Build ID: 20220630212430
### Steps to reproduce
1. Use a new profile. Leave all settings as default. Make sure `dom.indexedDB.hide_in_pbmode.enabled` is set to `true`.
2. Open a Private Browsing Window.
3. Visit https://lihkg.com or https://forum.hkgolden.com/. (2 popular Hong Kong discussion forums in Chinese)
### Actual result
The content windows for both forums are showing blank.
### Expected result
Both should load properly.
### Workaround
Set only `dom.indexedDB.hide_in_pbmode.enabled` to `false`.
`dom.caches.hide_in_pbmode.enabled` or `dom.serviceWorkers.hide_in_pbmode.enabled` can be left as `true`.
### Regression
Last good Nightly: 2022-06-29
First bad Nightly: 2022-06-30
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=401c2d7e80fba6483348d1d0514c768f7180e734&tochange=65f99678a1efc85ec58cae26d8762fcfbd702a9d
Bisecting autoland builds:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=80116c1aa5c8532275bdd113ce2c431df4f0d994&tochange=e64c83e9d62d19e3f8da181736595423b2bddb52
This is regressed by bug 1776109.
|
|
1,777,693 | 15,967,674 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0
Steps to reproduce:
1. Open any pdf with Nightly, viewer works.
2. Click print icon, print preview is blank.
3. Click print button, prints blank pages.
Actual results:
Updated Nightly, still prints blanks.
cleared printer settings in menu, same.
setup new profile, same.
Adjusted print settings, same.
System Dialog box shows print preview, still prints blanks.
Other browsers (including regular Firefox) work.
Other apps work.
Expected results:
Expected a normal print. This worked fine up to a couple of days ago. Hasn't worked since. I love Firefox, look forward to having this fixed, let me know if I can help.
|
|
1,778,068 | 15,971,830 |
Created attachment 9284102
test.pdf
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
1. Set browser.display.background_color to #FFFF00
2. Open a PDF file that has a usual background (i.e. white, as generated by pdflatex, but I don't know the internals; just in case, I have attached a small PDF file to reproduce the issue).
Actual results:
The background of the PDF document is what is specified by browser.display.background_color, e.g. yellow (#FFFF00) with the above test.
Expected results:
The background of the PDF document should be white.
Note: this is a recent regression (appearing with FF 102?).
|
|
1,778,237 | 15,973,204 |
Steps to reproduce:
1. Open https://isekai-yakkyoku.jp/ and wait for page loading
2. Click playback button
Actual results:
Firefox102.0.0 and Nightly104.0a1 eats up memory and Hangs. OS also becomes unresponsive.
Chrome works as expected and has low memory consumption.
Firefox 91.11.0 play video sometimes normally but peak memory usage is very large, almost 100% of physical memory.
No problem when playing the original embedded video on youtube site.
Expected results:
Playback correctly
|
|
1,778,335 | 15,973,885 |
Created attachment 9284345
First suggestion has additional http prefix
STR:
1. Type `https://mozilla.org/` into the address bar, including the trailing slash (site needs to autofill and have a www subdomain).
Expected:
First suggested item is `https://mozilla.org/ — Visit` or `https://www.mozilla.org/ — Visit`.
Actual:
After typing the trailing slash, the first suggestion becomes `httphttps://mozilla.org/ — Visit`, having an additional `http` prefix. Pressing Enter does a web search or tries to open the `httphttps:` protocol.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7769fe500298f839594d1c1a3782ad23b5d5926e&tochange=58d8e3010b7739779b9651e8c213c5865601b49a
Regressed by Bug 1770095.
|
|
1,778,452 | 15,974,853 |
Created attachment 9284473
Actual.png
Firefox Nighty 104.0a1 (2022-07-06) (64-Bit)
macOS
Steps to reproduce:
1) Type something into the Address Bar
2) Take look at the Resultlist
Expected: The results should be vertically aligned with Address Bar Input Text.
Actual: They are no longer vertically aligned.
This is a recent regression.
|
|
1,778,463 | 15,974,931 |
Created attachment 9284483
issue pin.gif
**Found in**
* Beta 103.0b5
**Affected versions**
* latest Nightly 104.0a1
* Beta 103.0b5
**Affected platforms**
* Windows 7 x64
**Steps to reproduce**
1. Double click on the Firefox Setup.
2. Click on the "Run" button from the dialog.
3. Click on the "Next" button from the installation wizard.
4. Choose the custom installation and hit Next.
5. Leave the default installation path, then hit Next once again.
6. Uncheck the "On my taskbar" checkbox.
7. Finish the installation process.
8. Observe the Win 7 taskbar.
**Expected result**
* Firefox icon is not pinned to the taskbar.
**Actual result**
* Firefox icon is pinned to the taskbar.
**Regression range**
* Not a regression, the bug can be reproduced on the first builds where this feature landed, e.g. Nightly from 2022-06-28.
**Additional notes**
* This can be reproduced if all Firefox profiles, files are deleted from %appdata%. It did not seem to make any difference if deleting the Mozilla registry files as well.
* We were unable to reproduce this on Win 10 x64 or Win 8.1 x64.
|
|
1,778,484 | 15,975,092 |
Steps to reproduce:
1) Open https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf
2) Get to Print Dialog (CTRL+P) and Save as PDF
3) Open Saved File
4) Select and copy Text (Dummy PDF file) from the saved pdf file
5) Paste it somewhere
Result: Unrecognized characters
Expected: "Dummy PDF file" text
|
|
1,778,714 | 15,977,281 |
Created attachment 9284701
Screenplay.gif
**Found in**
Firefox 103.0b6
**Affected versions**
Firefox 103.0b6
Firefox 104.0a1
**Affected platforms**
Windows 10
macOS10.13
Ubuntu 20.04
**Steps to reproduce**
1. Open FF.
2. Open pdf file. (I used "http://www.pdf995.com/samples/pdf.pdf ").
3. Download pdf.
4. Open download file (Library).
5. Right click on the downloaded pdf 'Copy Download link'.
6. Paste the copied link to a new tab.
**Expected result**
Copied file should be “http://www.pdf995.com/samples/pdf.pdf”.
**Actual result**
Copied file is "blob:resource://pdf.js/9f79bca1-df79-4060-b207-24dd3f6d5374".
**Regression range**
Will add as soon as possible.
**Additional notes**
* The issue is related to bug 1766030.
* Issue is fixed if downloaded panel is reached from the toolbar button. Only reproducible if downloaded panel is reached from the Library view.
|
|
1,768,750 | 15,893,549 |
STR:
1. Launch FF, go to google.com
2. Change the zoom level from the default zoom with cmd/ctrl + or cmd/ctrl -
3. Focus the URL bar with cmd/ctrl + L
4. Hit tab
Expected: the zoom indicator receives a focus outline
Actual: no focus outline is drawn
I ran mozregression, which pointed me here: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6c069b46b57f9ef2da16aa9487a6f7544507b212&tochange=91956f62a123375565ab58f96f50b6245dd381b8
|
|
1,769,309 | 15,897,834 |
Breaking this out as a separate thing from bug 1752733.
This particular signature has spiked because of win32k lockdown.
I had seen it briefly in extracts, but it always disappeared because the same signature occurs without win32k lockdown, but it would seem nowhere near as much.
My suspicion is that these are older versions of HitmanPro Alert that are still linked to user32.dll and possibly try to use win32k APIs.
I'll see if blocking the current version works and if it does block from the last version for which we're actually seeing crashes in the content process.
Crash report: https://crash-stats.mozilla.org/report/index/c38efb33-8cd5-4ac9-9741-f7a6e0220513
Reason: ```EXCEPTION_ACCESS_VIOLATION_WRITE```
Top 10 frames of crashing thread:
```
0 hmpalert.dll hmpalert.dll@0x000000000002ae5e
1 hmpalert.dll hmpalert.dll@0x0000000000028621
2 kernelbase.dll ReadProcessMemory
3 kernelbase.dll <unknown in kernelbase.dll>
4 kernelbase.dll K32EnumProcessModules
5 xul.dll static SharedLibraryInfo::GetInfoForSelf tools/profiler/core/shared-libraries-win32.cc:138
6 xul.dll mozilla::Telemetry::BatchProcessedStackGenerator::BatchProcessedStackGenerator toolkit/components/telemetry/other/ProcessedStack.cpp:72
7 xul.dll mozilla::UntrustedModulesProcessor::CompleteProcessing toolkit/xre/dllservices/UntrustedModulesProcessor.cpp:876
8 xul.dll mozilla::MozPromise<mozilla::Maybe<mozilla::UntrustedModulesProcessor::ModulesMapResultWithLoads>, nsresult, 1>::ThenValue<`lambda at /builds/worker/checkouts/gecko/toolkit/xre/dllservices/UntrustedModulesProcessor.cpp:563:9', `lambda at /builds/worker/checkouts/gecko/toolkit/xre/dllservices/UntrustedModulesProcessor.cpp:572:9'>::DoResolveOrRejectInternal xpcom/threads/MozPromise.h:846
9 xul.dll mozilla::MozPromise<CopyableTArray<bool>, bool, 0>::ThenValueBase::ResolveOrRejectRunnable::Run xpcom/threads/MozPromise.h:487
```
|
|
1,769,747 | 15,903,155 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
We're seeing poor performance on Vimeo while viewing very high quality 360 video.
It looks like Vimeo do 360 by decoding a large video, and using webgl to transform it to a 2D viewport.
I'm getting this error on my MacBook Pro 2020
STR:
1. Load 360 video on Vimeo, i.e.: https://vimeo.com/channels/360vr/355120249
2. Select 4K from the cog menu
3. You can see the lower framerate of the video in comparison with chrome.
Actual results:
Video has low framerate in comparison to chrome
Expected results:
The video should have a good framerate
|
|
1,770,010 | 15,905,409 |
From github: https://github.com/mozilla-mobile/fenix/issues/25269.
> ### Steps to reproduce
>
> 1. Be sure your Android Bitwarden app is locked **and killed*. (i.e. If you open the app, it should prompt you for master password or biometric auth; if it does so, that's good -- leave it in that state, and kill the app by swiping it offscreen from your app-switcher UI). In the event you've unlocked it, lock it via its "Settings|Lock Now" button, and then kill the app.
> 2. In Fenix, visit some site where Bitwarden has a saved login that you could use, e.g. in my case I'm using https://wiki.mozilla.org/index.php?title=Special:UserLogin
> 3. Tap the website's username field
> 4. Keyboard will appear, with a "Bitwarden Vault is locked" button at the top. Tap that button.
> 5. Authenticate with Bitwarden. It will probably then say "Items for mozilla.org" (or whatever site you're on).
> 6. Tap its entry for the credentials that you want to use. (This makes Bitwarden disappear and Firefox becomes foreground again.)
>
> ### Expected behaviour
>
> The username/password field should have been filled in.
> Also, my keyboard should have buttons for the various matching logins in Bitwarden, now that I've unlocked it. (This is what happens if I reload at this point and focus the username or password field, i.e. if I perform the STR with Bitwarden already focused.)
>
>
> ### Actual behaviour
>
> The username field is still empty.
> The password field has gained focus, but is also empty.
> My keyboard does not have any Bitwarden buttons anymore.
>
>
> ### Device name
>
> Google Pixel 4a
>
> ### Android version
>
> Android 12
>
> ### Firefox release type
>
> Firefox Nightly
>
> ### Firefox version
>
> 102.0a1
>
> ### Device logs
>
> _No response_
>
> ### Additional information
>
> Note that in Bitwarden settings, under "Auto-fill Services", I have every option enabled.
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,770,409 | 15,907,916 |
Created attachment 9277476
GetFirefoxMobile_newTab.gif
**[Affected versions]:**
- Firefox Release 100.0.1 (Build ID: 20220513165813)
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
- macOS 12.3.1
**[Prerequisites]:**
- Have the Firefox Release browser, en* locale installed.
- Have a new Firefox profile created.
- Have the “nimbus.debug” pref set to true.
**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to the ‘about:studies?optin_slug=download-mobile-regular-eco2204-en&optin_branch=treatment-a&optin_collection=nimbus-preview’ URL.
3. Restart the browser.
4. Click the “Send me a link” button from the “Download Firefox Mobile” spotlight.
5. Observe the behavior of the newly opened tab.
**[Expected result]:**
- The opened tab is focused.
**[Actual result]:**
- The “Get Firefox Mobile” page is opened but is not focused.
**[Notes]:**
- Attached is a screen recording of the issue.
|
|
1,770,750 | 15,911,563 |
Created attachment 9277785
ferpa-2020 (4)-1.pdf
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
Edit a pdf document in firefox, and hit save or download.
Actual results:
Changes are not persistent.
Expected results:
Hitting save/download should change the file. It works fine in chrome, so I know it's a firefox issue, not a pdf issue.
|
|
1,771,024 | 15,913,942 |
Recent regression.
Steps to reproduce:
1. Login to reddit (or bugzilla, or github, or element - I used reddit)
2. enable "Delete cookies and site data when Nightly is closed"
3. ensure that the site permission for reddit (via the page info dialog) is set to "allow" for "set cookies"
4. kill firefox via a task manager (not a clean quit)
5. start Firefox
What happens:
I am logged out from reddit.
Expected result:
I am still logged into reddit, as was the case prior to regression.
7:54.23 INFO: Narrowed integration regression window from [5da87985, cda9c3f8] (3 builds) to [3a23a97d, cda9c3f8] (2 builds) (~1 steps left)
7:54.23 INFO: No more integration revisions, bisection finished.
7:54.23 INFO: Last good revision: 3a23a97debf3c86cf70927df8cefa0e44fdd7e5d
7:54.23 INFO: First bad revision: cda9c3f8950b0fcb826af8f7c0516275c8c0f7b2
7:54.23 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3a23a97debf3c86cf70927df8cefa0e44fdd7e5d&tochange=cda9c3f8950b0fcb826af8f7c0516275c8c0f7b2
|
|
1,771,054 | 15,914,158 |
+++ This bug was initially created as a clone of Bug #1721220 +++
bug 1721220 modifies GeckoView to pass the TLS error state through, but we will still need Fenix UI code changes using that change to actually fix the reported bug. Filing this to track that state for advisory and bug bounty purposes because it looks like the GeckoView bug will be closed a release earlier (at least) than the actual security problem is fixed.
|
|
1,763,996 | 15,852,006 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.75 Safari/537.36
Steps to reproduce:
###### Version
```
C96.0
```
###### Execution steps
/root/.jsvu/spidermonkey Testcase.js
Actual results:
###### Test case 1
```
var foo = function (t1) {
t1.sort(function (a, b) {
return a - b;
});
print(t1);
}
var Parameter1 = ['a','b'];
foo(Parameter1);
```
###### Output 1
```
b,a
```
###### Test case 2
```
var foo = function (t1) {
t1.sort(function (a, b) {
print(a - b);
//print(1);
return a - b;
});
print(t1);
}
var Parameter1 = ['a','b'];
foo(Parameter1);
```
###### Output 2
```
NaN
a,b
```
Expected results:
###### Description
If the sort function only contains a return statement and the return value is `NaN`, the reversed array is output. If the sort function contains other statements in addition to the `return NaN` statement, the original array is output. Why are their outputs different?
|
|
1,764,064 | 15,853,957 |
Created attachment 9271681
rec of the issue2.gif
**[Affected versions]:**
- Firefox Beta 100.0b4 - Build ID: 20220410195727
- Firefox Nightly 101.0a1 - Build ID: 20220410213958
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have a new Fireofox profile with the following prefs in the "about:config" page:
- "devtools.chrome.enabled" set to "true";
- "browser.ping-centre.log" set to "true"
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Open the "Browser Console" (Ctrl + Shift + J).
3. Run the following command `Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog()` in the "Browser Console".
4. Focus the browser and press the "Esc" key.
5. Focus the "Browser Console" and observe the displayed pings.
**[Expected result]:**
- A "DISMISS" ping specific to the "FX_100_UPGRADE" spotlight is displayed.
**[Actual result]:**
- There is no "DISMISS" telemetry ping displayed.
**[Additional Notes]:**
- Attached a screen recording of the issue:
|
|
1,764,070 | 15,853,972 |
Created attachment 9271682
autodismiss telemetry.gif
**[Affected Versions]:**
- Firefox Beta 100.b4 (Build ID: 20220410195727)
- Firefox Nightly 101.0a1 (Build ID: 20220410213958)
**[Affected Platforms]:**
- Windows 10
- macOS 11.6
- Linux Mint 20.2
**[Prerequisites]:**
- Have Firefox installed and open.
- Have Firefox set as default browser and pinned if possible.
- Have “devtools.chrome.enabled” set to “true” from “about:config”.
- Have “browser.ping-centre.log” set to “true” from “about:config”.
**[Steps to reproduce]:**
1. Open the Browser Console (Ctrl + Shift + J).
2. Run the following command “Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog()” in the Browser Console.
3. Wait for the upgrade dialog to be autodismissed.
4. Observe the ping displayed in the Browser Console.
**[Expected result]:**
- A dismiss ping is displayed.
**[Actual result]:**
- A “CLICK_BUTTON” event with the “primary_button” source is displayed.
**[Notes]:**
- Attached is a recording of the issue.
|
|
1,764,171 | 15,854,752 |
Created attachment 9271783
ff-devtools-grid-enabled.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.75 Safari/537.36
Steps to reproduce:
Example code:
https://codepen.io/mw_codes/pen/jOYxvQN
Check the example on Firefox and the other browsers (Chrome etc.).
I created a wrapper that contains three <a> tags.
The wrapper has:
display: grid;
grid-auto-flow: column;
grid-auto-columns: max-content;
and there is more than enough space to display its child-elements in columns.
The <a> tag has:
max-width: max-content;
padding: 8px 16px;
box-sizing: border-box;
Actual results:
The grid auto columns won't count the inline padding to the element's width and the text inside <a> tags will wrap like there was not enough space to fit the text in one line.
When we add white-space: nowrap, the text will overflow.
When we change the box-sizing property from border-box (that counts paddings to the overall element's width) to content-box (that doesn't count paddings to the overall element's width) the problem disappears.
The bug appears only on Firefox.
The bug doesn't appear on Chrome.
Expected results:
The text inside <a> tags should not wrap to the next lines or overflow if there is enough space to fit every <a> tag inside the wrapper (just like in Chrome).
|
|
1,764,341 | 15,855,890 |
Created attachment 9271937
PB_FOCUS_PROMO modal is not responsive.gif
**[Affected versions]:**
- Firefox Nightly 101.0a1 (Build ID: 20220408094506)
- Firefox Beta 100.0b4 (Build ID: 20220410195727)
**[Affected Platforms]:**
- Mac 10.15.7
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the latest Firefox Nightly/Beta 100 browser installed.
- Have a new Firefox profile.
**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Open a Private Window.
3. Resize the browser vertically and horizontally to 25% of its width.
4. Observe the modal.
**[Expected result]:**
- All the elements from the modal are visible and displayed.
OR
- There are scrollbars available in order to scroll the modal to see all the elements.
**[Actual result]:**
- There are elements from the modal that are not visible and the modal cannot be scrolled.
[Notes]:
- Attached is a screen recording of the issue.
|
|
1,764,451 | 15,856,928 |
+++ This bug was initially created as a clone of Bug #1763874 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
Steps to reproduce:
```
mach jstests Record/cross-realm --args=--more-compartments
```
Actual results:
```
## non262/Record/cross-realm.js: rc = -11, run time = 0.380883
Assertion failure: vp.isObject(), at /home/tjc/gecko-fork/js/src/vm/Compartment-inl.h:69
#01: JS::Compartment::wrap(JSContext*, JS::MutableHandle<JS::Value>)[/home/tjc/gecko-fork/obj-x64-debug/dist/bin/js +0x1b32596]
#02: js::CrossCompartmentWrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const[/home/tjc/gecko-fork/obj-x64-debug/dist/bin/js +0x1e1e4be]
#03: ???[/home/tjc/gecko-fork/obj-x64-debug/dist/bin/js +0x1e257eb]
```
Expected results:
The test should pass. I have a patch coming shortly.
|
|
1,764,535 | 15,857,443 |
**[Affected versions]:**
- Firefox Beta 100.0b5 (Build ID: 20220412185818)
**[Affected Platforms]:**
- Windows 10 x64
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the latest Firefox Beta 100 browser, ar locale installed/extracted.
- Have the OS language set to Central Kurdish.
- Have a new Firefox profile.
**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Observe the “about:welcome” page.
**[Expected result]:**
- The “about:welcome” page is correctly displayed.
**[Actual result]:**
- The “about:welcome” page is broken and contains only the background image.
**[Notes]:**
- This issue is not reproducible on Nightly builds.
- I didn’t manage to reproduce this issue on macOS.
- This issue is still reproducible after restarting the browser.
- Attached is a screen recording of the issue: [link](https://drive.google.com/file/d/15_a0iIfQbOM6sM37qlaJAFlFNUr-H2WC/view?usp=sharing).
|
|
1,764,715 | 15,858,865 |
The following testcase crashes on mozilla-central revision 20220411-87b37ed2950d (debug build, run with --fuzzing-safe --cpu-count=2 --ion-offthread-compile=off):
r(`
while (true) {
var line = y.shift();
if (y.shift() == null) {
let m94 = parseModule(undefined);
for (var i72 = 0; i72 < 5; i72++)
a1 = strictAssign();
}
a3 = class extends a93?.b34 {}.get();
}
`);
function r(src) {
oomTest(function() {
let m = parseModule(src);
});
}
Backtrace:
received signal SIGSEGV, Segmentation fault.
0x00005555574989be in js::frontend::OptionalEmitter::emitOptionalJumpTarget(JSOp, js::frontend::OptionalEmitter::Kind) ()
#0 0x00005555574989be in js::frontend::OptionalEmitter::emitOptionalJumpTarget(JSOp, js::frontend::OptionalEmitter::Kind) ()
#1 0x0000555557458ba7 in js::frontend::BytecodeEmitter::emitOptionalChain(js::frontend::UnaryNode*, js::frontend::ValueUsage) ()
#2 0x000055555743fd66 in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#3 0x000055555744692b in js::frontend::BytecodeEmitter::emitClass(js::frontend::ClassNode*, js::frontend::BytecodeEmitter::ClassNameKind, js::frontend::TaggedParserAtomIndex) ()
#4 0x000055555743fec7 in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#5 0x000055555743f49f in js::frontend::BytecodeEmitter::emitPropLHS(js::frontend::PropertyAccess*) ()
#6 0x000055555745717e in js::frontend::BytecodeEmitter::emitCalleeAndThis(js::frontend::ParseNode*, js::frontend::ParseNode*, js::frontend::CallOrNewEmitter&) ()
#7 0x00005555574581e2 in js::frontend::BytecodeEmitter::emitCallOrNew(js::frontend::CallNode*, js::frontend::ValueUsage) ()
#8 0x000055555743f91d in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#9 0x000055555744ac25 in js::frontend::BytecodeEmitter::emitAssignmentOrInit(js::frontend::ParseNodeKind, js::frontend::ParseNode*, js::frontend::ParseNode*) ()
#10 0x000055555743f8bb in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#11 0x0000555557453200 in js::frontend::BytecodeEmitter::emitExpressionStatement(js::frontend::UnaryNode*) ()
#12 0x000055555743fba5 in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#13 0x000055555745304f in js::frontend::BytecodeEmitter::emitStatementList(js::frontend::ListNode*) ()
#14 0x000055555743fd96 in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#15 0x000055555744d68e in js::frontend::BytecodeEmitter::emitLexicalScope(js::frontend::LexicalScopeNode*) ()
#16 0x000055555743fafe in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#17 0x0000555557450811 in js::frontend::BytecodeEmitter::emitWhile(js::frontend::BinaryNode*) ()
#18 0x000055555743fe3b in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#19 0x000055555745304f in js::frontend::BytecodeEmitter::emitStatementList(js::frontend::ListNode*) ()
#20 0x000055555743fd96 in js::frontend::BytecodeEmitter::emitTree(js::frontend::ParseNode*, js::frontend::ValueUsage, js::frontend::BytecodeEmitter::EmitLineNumberNote) ()
#21 0x00005555574434c2 in js::frontend::BytecodeEmitter::emitScript(js::frontend::ParseNode*) ()
#22 0x000055555746a8ee in ModuleCompiler<char16_t>::compile(JSContext*) ()
#23 0x000055555746a303 in bool ParseModuleToStencilAndMaybeInstantiate<char16_t>(JSContext*, js::frontend::CompilationInput&, JS::SourceText<char16_t>&, mozilla::Variant<mozilla::UniquePtr<js::frontend::ExtensibleCompilationStencil, JS::DeletePolicy<js::frontend::ExtensibleCompilationStencil> >, RefPtr<js::frontend::CompilationStencil>, js::frontend::CompilationGCOutput*>&) ()
#24 0x0000555557434019 in js::frontend::CompileModule(JSContext*, JS::ReadOnlyCompileOptions const&, JS::SourceText<char16_t>&) ()
#25 0x0000555556b67b3e in ParseModule(JSContext*, unsigned int, JS::Value*) ()
#26 0x00002504b4fef0df in ?? ()
[...]
#30 0x0000000000000000 in ?? ()
rax 0x5555557fb8a5 93824995014821
rbx 0x7fffffff8c30 140737488325680
rcx 0x555558207138 93825039102264
rdx 0x0 0
rsi 0x7ffff7105770 140737338431344
rdi 0x7ffff7104540 140737338426688
rbp 0x7fffffff8c20 140737488325664
rsp 0x7fffffff8c00 140737488325632
r8 0x7ffff7105770 140737338431344
r9 0x7ffff7f99840 140737353717824
r10 0x0 0
r11 0x0 0
r12 0x1 1
r13 0x0 0
r14 0x1 1
r15 0x0 0
rip 0x5555574989be <js::frontend::OptionalEmitter::emitOptionalJumpTarget(JSOp, js::frontend::OptionalEmitter::Kind)+238>
=> 0x5555574989be <_ZN2js8frontend15OptionalEmitter22emitOptionalJumpTargetE4JSOpNS1_4KindE+238>: movl $0x80,0x0
0x5555574989c9 <_ZN2js8frontend15OptionalEmitter22emitOptionalJumpTargetE4JSOpNS1_4KindE+249>: callq 0x555556bcb517 <abort>
This is an OOM but the assertion doesn't look good and varies based on the testcase (and the fact that it requires an OOM condition doesn't necessarily make it less exploitable). Marking this s-s until investigated further.
|
|
1,764,890 | 15,860,106 |
Created attachment 9272454
scrollbar_refresh.gif
**[Affected versions]:**
- Firefox Nightly 101.0a1 (Build ID: 20220414214512)
- Firefox Beta 100.0b6 (Build ID: 20220414190112)
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the latest Firefox Beta 100 browser installed/extracted.
- Have a new Firefox profile.
**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Refresh the “about:welcome” page and observe the bottom-right part of the page.
**[Expected result]:**
- The page is refreshed and all the elements are correctly displayed.
**[Actual result]:**
- An extra scrollbar is present.
**[Regression Window]:**
- The issue is not reproducible on the older Nightly 100.0a1 build. Considering this using mozregression tools I have found the regression range. Here are the results:
Last good revision: 660bc4607826fa9c262c73b424eeb6f9361ba2d5
First bad revision: 6c7a66cae86bc995159261e5f77e83450df8d3cf
Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=660bc4607826fa9c262c73b424eeb6f9361ba2d5&tochange=6c7a66cae86bc995159261e5f77e83450df8d3cf)
@Greg could you please take a look over this regression window since I am not sure which bug has caused this issue?
**[Notes]:**
- Attached is a screen recording of the issue.
|
|
1,765,130 | 15,863,115 |
Created attachment 9272672
graciasString.PNG
**[Affected versions]:**
- Firefox Nightly 101.0a1 (Build ID: 20220417212536)
- Firefox Beta 100.0b7 (Build ID: 20220417185951)
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.5
- Ubuntu 20.04 x64
**[Prerequisites]:**
- Have the latest Firefox Beta 100 browser, es-ES build installed/extracted.
- Have the “devtools.chrome.enabled” pref set to true.
- Have the “Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog()” syntax copied to clipboard.
- Have a new Firefox profile.
**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Focus the browser console and run the syntax from prerequisites.
3. Observe the “gracias” string from the spotlight’s title.
**[Expected result]:**
- The “gracias” string is entirely visible.
**[Actual result]:**
- The bottom part of the “g” letter from the “gracias” string is cut off.
**[Notes]:**
- This issue is reproducible using all the browser’s themes.
- This “gracias” string is fully visible on High Contrast mode.
- Attached is a screenshot of the issue.
|
|
1,765,140 | 15,863,179 |
Created attachment 9272681
download_mixed.gif
*Affected versions*
* 101.0a1 (20220418091627)
* 100.0b4
* 99.0.1
*Affected platforms*
* Windows 10x64
* macOS 10.15
* Ubuntu 21.04
*Steps to reproduce*
1. Open https://www.thinkbroadband.com/download.
Click on two items to download (e.g click on Extra Small File (5MB) and on Small File (10MB))
2. Open the download panel from the toolbar and click on the Extra Small File (5MB).
3. Click to Allow/ Remove download and observe the download panel.
*Expected result*
* The selected file is downloaded/ removed.
*Actual result*
* First file is downloaded/ removed.
*Regression range*
* Last good revision: 92c286a2adf98e61802ff7a5de2dd10609959d0a
First bad revision: 2375d7340e84f802ed98fa68289153e036c63b63
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=92c286a2adf98e61802ff7a5de2dd10609959d0a&tochange=2375d7340e84f802ed98fa68289153e036c63b63
*Notes*
* Attached a screen recording.
* Due to first item being always acted upon, Allow Download in case of mixed content only works once, the subsequent tries to allow download (in case of multiple downloads blocked) will attempt to allow first item already being downloaded, though leading to a broken Allow Download.
|
|
1,765,339 | 15,864,709 |
Testcase found while fuzzing mozilla-central rev 61d8c578d367 (built with: --enable-debug --enable-fuzzing).
Testcase can be reproduced using the following commands:
```
$ pip install fuzzfetch grizzly-framework
$ python -m fuzzfetch --build 61d8c578d367 --debug --fuzzing -n firefox
$ python -m grizzly.replay ./firefox/firefox testcase.html
```
```
Assertion failure: !aArgument.IsUncatchableException() (Doesn't make sense to convert uncatchable exception to a JS value!), at /dom/bindings/ToJSValue.cpp:55
==2172129==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7ff1473302df bp 0x7ff139d307d0 sp 0x7ff139d307c0 T2172192)
==2172129==The signal is caused by a WRITE memory access.
==2172129==Hint: address points to the zero page.
#0 0x7ff1473302df in mozilla::dom::ToJSValue(JSContext*, mozilla::ErrorResult&&, JS::MutableHandle<JS::Value>) /dom/bindings/ToJSValue.cpp:53:3
#1 0x7ff148c3b9a4 in mozilla::dom::PipeToPump::ShutdownWithActionAfterFinishedWrite(JSContext*, already_AddRefed<mozilla::dom::Promise> (*)(JSContext*, mozilla::dom::PipeToPump*, JS::Handle<mozilla::Maybe<JS::Value> >, mozilla::ErrorResult&), JS::Handle<mozilla::Maybe<JS::Value> >) /dom/streams/ReadableStreamPipeTo.cpp:509:15
#2 0x7ff148c3a3b9 in mozilla::dom::PipeToPump::ShutdownWithAction(JSContext*, already_AddRefed<mozilla::dom::Promise> (*)(JSContext*, mozilla::dom::PipeToPump*, JS::Handle<mozilla::Maybe<JS::Value> >, mozilla::ErrorResult&), JS::Handle<mozilla::Maybe<JS::Value> >) /dom/streams/ReadableStreamPipeTo.cpp:429:3
#3 0x7ff148c3abc2 in mozilla::dom::PipeToPump::OnDestClosed(JSContext*, JS::Handle<JS::Value>) /dom/streams/ReadableStreamPipeTo.cpp
#4 0x7ff148c3a64a in mozilla::dom::PipeToPump::SourceOrDestErroredOrClosed(JSContext*) /dom/streams/ReadableStreamPipeTo.cpp:283:5
#5 0x7ff148c3ad50 in mozilla::dom::PipeToPump::Start(JSContext*, mozilla::dom::AbortSignal*) /dom/streams/ReadableStreamPipeTo.cpp:319:7
#6 0x7ff148c3167d in mozilla::dom::ReadableStreamPipeTo(mozilla::dom::ReadableStream*, mozilla::dom::WritableStream*, bool, bool, bool, mozilla::dom::AbortSignal*, mozilla::ErrorResult&) /dom/streams/ReadableStreamPipeTo.cpp:958:9
#7 0x7ff148c3221f in mozilla::dom::ReadableStream::PipeTo(mozilla::dom::WritableStream&, mozilla::dom::StreamPipeOptions const&, mozilla::ErrorResult&) /dom/streams/ReadableStream.cpp:812:10
#8 0x7ff1467174ad in pipeTo /builds/worker/workspace/obj-build/dom/bindings/ReadableStreamBinding.cpp:678:60
#9 0x7ff1467174ad in mozilla::dom::ReadableStream_Binding::pipeTo_promiseWrapper(JSContext*, JS::Handle<JSObject*>, void*, JSJitMethodCallArgs const&) /builds/worker/workspace/obj-build/dom/bindings/ReadableStreamBinding.cpp:692:13
#10 0x7ff147314628 in bool mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ConvertExceptionsToPromises>(JSContext*, unsigned int, JS::Value*) /dom/bindings/BindingUtils.cpp:3270:13
#11 0x7ff14c762f4f in CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::CallReason, JS::CallArgs const&) /js/src/vm/Interpreter.cpp:420:13
#12 0x7ff14c7627bd in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) /js/src/vm/Interpreter.cpp:507:12
#13 0x7ff14c763bfe in InternalCall(JSContext*, js::AnyInvokeArgs const&, js::CallReason) /js/src/vm/Interpreter.cpp:567:10
#14 0x7ff14c759d76 in CallFromStack /js/src/vm/Interpreter.cpp:571:10
#15 0x7ff14c759d76 in Interpret(JSContext*, js::RunState&) /js/src/vm/Interpreter.cpp:3293:16
#16 0x7ff14c750bc3 in js::RunScript(JSContext*, js::RunState&) /js/src/vm/Interpreter.cpp:389:13
#17 0x7ff14c7626b8 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) /js/src/vm/Interpreter.cpp:539:13
#18 0x7ff14c763bfe in InternalCall(JSContext*, js::AnyInvokeArgs const&, js::CallReason) /js/src/vm/Interpreter.cpp:567:10
#19 0x7ff14c763e01 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>, js::CallReason) /js/src/vm/Interpreter.cpp:584:8
#20 0x7ff14b3f1f61 in JS::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::HandleValueArray const&, JS::MutableHandle<JS::Value>) /js/src/vm/CallAndConstruct.cpp:117:10
#21 0x7ff14702db1c in mozilla::dom::EventHandlerNonNull::Call(mozilla::dom::BindingCallContext&, JS::Handle<JS::Value>, mozilla::dom::Event&, JS::MutableHandle<JS::Value>, mozilla::ErrorResult&) /builds/worker/workspace/obj-build/dom/bindings/EventHandlerBinding.cpp:283:37
#22 0x7ff1478a06d9 in void mozilla::dom::EventHandlerNonNull::Call<nsCOMPtr<mozilla::dom::EventTarget> >(nsCOMPtr<mozilla::dom::EventTarget> const&, mozilla::dom::Event&, JS::MutableHandle<JS::Value>, mozilla::ErrorResult&, char const*, mozilla::dom::CallbackObject::ExceptionHandling, JS::Realm*) /builds/worker/workspace/obj-build/dist/include/mozilla/dom/EventHandlerBinding.h:365:12
#23 0x7ff14789f88d in mozilla::JSEventHandler::HandleEvent(mozilla::dom::Event*) /dom/events/JSEventHandler.cpp:201:12
#24 0x7ff14788060b in mozilla::EventListenerManager::HandleEventSubType(mozilla::EventListenerManager::Listener*, mozilla::dom::Event*, mozilla::dom::EventTarget*) /dom/events/EventListenerManager.cpp:1316:22
#25 0x7ff1478812c9 in mozilla::EventListenerManager::HandleEventInternal(nsPresContext*, mozilla::WidgetEvent*, mozilla::dom::Event**, mozilla::dom::EventTarget*, nsEventStatus*, bool) /dom/events/EventListenerManager.cpp:1507:17
#26 0x7ff147875ff4 in HandleEvent /dom/events/EventListenerManager.h:395:5
#27 0x7ff147875ff4 in mozilla::EventTargetChainItem::HandleEvent(mozilla::EventChainPostVisitor&, mozilla::ELMCreationDetector&) /dom/events/EventDispatcher.cpp:348:17
#28 0x7ff147875517 in mozilla::EventTargetChainItem::HandleEventTargetChain(nsTArray<mozilla::EventTargetChainItem>&, mozilla::EventChainPostVisitor&, mozilla::EventDispatchingCallback*, mozilla::ELMCreationDetector&) /dom/events/EventDispatcher.cpp:550:16
#29 0x7ff147877d78 in mozilla::EventDispatcher::Dispatch(nsISupports*, nsPresContext*, mozilla::WidgetEvent*, mozilla::dom::Event*, nsEventStatus*, mozilla::EventDispatchingCallback*, nsTArray<mozilla::dom::EventTarget*>*) /dom/events/EventDispatcher.cpp:1119:11
#30 0x7ff14787a916 in mozilla::EventDispatcher::DispatchDOMEvent(nsISupports*, mozilla::WidgetEvent*, mozilla::dom::Event*, nsPresContext*, nsEventStatus*) /dom/events/EventDispatcher.cpp
#31 0x7ff14785167b in mozilla::DOMEventTargetHelper::DispatchEvent(mozilla::dom::Event&, mozilla::dom::CallerType, mozilla::ErrorResult&) /dom/events/DOMEventTargetHelper.cpp:180:17
#32 0x7ff147887dd2 in mozilla::dom::EventTarget::DispatchEvent(mozilla::dom::Event&) /dom/events/EventTarget.cpp:180:13
#33 0x7ff148b4a86f in mozilla::dom::MessageEventRunnable::DispatchDOMEvent(JSContext*, mozilla::dom::WorkerPrivate*, mozilla::DOMEventTargetHelper*, bool) /dom/workers/MessageEventRunnable.cpp:106:12
#34 0x7ff148b94ab2 in mozilla::dom::WorkerRunnable::Run() /dom/workers/WorkerRunnable.cpp:377:12
#35 0x7ff1443b52c9 in nsThread::ProcessNextEvent(bool, bool*) /xpcom/threads/nsThread.cpp:1174:16
#36 0x7ff1443bba4d in NS_ProcessNextEvent(nsIThread*, bool) /xpcom/threads/nsThreadUtils.cpp:465:10
#37 0x7ff148b83854 in mozilla::dom::WorkerPrivate::DoRunLoop(JSContext*) /dom/workers/WorkerPrivate.cpp:3133:7
#38 0x7ff148b6296a in mozilla::dom::workerinternals::(anonymous namespace)::WorkerThreadPrimaryRunnable::Run() /dom/workers/RuntimeService.cpp:2162:42
#39 0x7ff1443b52c9 in nsThread::ProcessNextEvent(bool, bool*) /xpcom/threads/nsThread.cpp:1174:16
#40 0x7ff1443bba4d in NS_ProcessNextEvent(nsIThread*, bool) /xpcom/threads/nsThreadUtils.cpp:465:10
#41 0x7ff144f65fa4 in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /ipc/glue/MessagePump.cpp:330:5
#42 0x7ff144e82507 in MessageLoop::RunInternal() /ipc/chromium/src/base/message_loop.cc:380:10
#43 0x7ff144e82412 in RunHandler /ipc/chromium/src/base/message_loop.cc:373:3
#44 0x7ff144e82412 in MessageLoop::Run() /ipc/chromium/src/base/message_loop.cc:355:3
#45 0x7ff1443b08d6 in nsThread::ThreadFunc(void*) /xpcom/threads/nsThread.cpp:378:10
#46 0x7ff15a016a57 in _pt_root /nsprpub/pr/src/pthreads/ptthread.c:201:5
#47 0x7ff15ad88608 in start_thread /build/glibc-sMfBJT/glibc-2.31/nptl/pthread_create.c:477:8
#48 0x7ff15a94f162 in __clone /build/glibc-sMfBJT/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
UndefinedBehaviorSanitizer can not provide additional info.
SUMMARY: UndefinedBehaviorSanitizer: SEGV /dom/bindings/ToJSValue.cpp:53:3 in mozilla::dom::ToJSValue(JSContext*, mozilla::ErrorResult&&, JS::MutableHandle<JS::Value>)
==2172129==ABORTING
```
|
|
1,765,442 | 15,865,679 |
Created attachment 9272935
Firefox 2022-04-20 00.10 profile.json.gz
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:99.0) Gecko/20100101 Firefox/99.0
Steps to reproduce:
I opened a page using many form fields with labels (in my case a lage json-editor https://github.com/json-editor/json-editor ) and entered some data in text fields / selected diffrent options of a <select>
UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:99.0) Gecko/20100101 Firefox/99.0
OS: Darwin 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
Device: Macbook Pro 15' 2017 i7 16GB
Actual results:
At some point (just after entering some string or switching an <select> to a diffrent option), the whole page (JS) freezes for 20-40 seconds. (see profile attached)
The page was deployed more than 50 days ago, so no dependency change there that caused this. Until a few days ago I never encountered this kind of lag after inital initalization of the editor, so I guess this was introduced in FF 99
Profiling shows 35 seconds (86%) spent in identifyAutofillFields -> ... -> findLabelElements
Expected results:
Like with previous versions of FF, the autofill machanic should not block the page noticable for the user, especially when the DOM mostly didn't change
|
|
1,765,760 | 15,867,578 |
Created attachment 9273227
Screenshot_2.png
**Environment:**
Operating System: Windows 10 PRO x64
Operating System: Mac OSX 10.15.6
Firefox version:Firefox Nightly 101.0a1 (2022-04-21) (64-bit)
**Preconditions:**
ETP set to STRICT
Clean profile
**Steps to reproduce:**
1. Navigate to: https://www.thetastebar.de/
2. Trigger the DevTools "Inspect element" option.
3. Observe the "Inspector" tab.
**Expected Behavior:**
DOM content is shown.
**Actual Behavior:**
DOM content is empty.
**Notes:**
- Not reproducible with ETP set to OFF.
- Works as expected using Chrome.
- Screenshot is attached.
|
|
1,765,835 | 15,868,075 |
From github: https://github.com/mozilla-mobile/fenix/issues/24901.
> ### Steps to reproduce
>
> 1. Use enableHighAccuracy in a browser app to display location on a map.
> 2. Walk around with FF open on Android phone.
> 3. Observe location -> you are up to 1000 m (!) away from your actual location.
> 4. Switch to a different gps app (e.g. Ingress). Switch to Firefox.
> 5. Notice the location becomes accurate.
>
> ### Expected behaviour
>
> Firefox should give me accuracy around 5-10 meters when I'm outside and in good weather.
>
> ### Actual behaviour
>
> So it seems like Firefox fails to ask for high accuracy GPS. In the current state of things there is no point in showing my location on a city map. Note that I used the same code before and it worked fine. I used to have better accuracy indoors (under a roof) in old Firefox.
>
> ### Device name
>
> Samsung s10e
>
> ### Android version
>
> Android 12, One UI 4.1
>
> ### Firefox release type
>
> Firefox Nightly
>
> ### Firefox version
>
> 101.0a1
>
> ### Device logs
>
> _No response_
>
> ### Additional information
>
> Example code:
>
> ```
> SelfLocation.prototype.setupWatch = function() {
> var me = this;
> function success(location) {
> me.receiver(location);
> }
> function error(err) {
> console.warn('location error(' + err.code + '): ' + err.message);
> }
> // see: https://developer.mozilla.org/en-US/docs/Web/API/PositionOptions
> var options = {
> enableHighAccuracy: true, // Ingress will probably enfoce it anyway
> //timeout: 5000,
> maximumAge: 0 // we want real position, no cache
> };
> this._watchId = navigator.geolocation.watchPosition(success, error, options);
> };
> ```
>
> See also:
> https://github.com/Eccenux/iitc-plugin-self-location
> You can install main iitc plugin from here:
> https://iitc.app/build/release/total-conversion-build.user.js
> And then open:
> https://intel.ingress.com/intel
>
> Oh, you would have to use FF Nightly builds to test this in IITC because you don't allow Tampermonkey on a standard FF mobile ☹...
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,766,022 | 15,869,248 |
Crash with win32k lockdown.
Crash report: https://crash-stats.mozilla.org/report/index/21f66228-bcb8-4199-b918-893b90220420
Reason: ```EXCEPTION_ACCESS_VIOLATION_READ```
Top 10 frames of crashing thread:
```
0 gdi32.dll gdi32.dll@0x0000000000004377
1 d3d9.dll CEnum::CEnum
2 d3d9.dll long Direct3DCreate9Impl
3 d3d9.dll Direct3DCreate9
4 videocapturerhk64.dll videocapturerhk64.dll@0x0000000000037219
5 videocapturerhk64.dll videocapturerhk64.dll@0x0000000000012e42
6 videocapturerhk64.dll videocapturerhk64.dll@0x0000000000089db3
7 videocapturerhk64.dll videocapturerhk64.dll@0x0000000000049d56
8 videocapturerhk64.dll videocapturerhk64.dll@0x000000000004d000
9 videocapturerhk64.dll videocapturerhk64.dll@0x00000000000b1d27
```
|
|
1,766,127 | 15,869,933 |
This has been detected by Raptor tests and was also reported by Fenix users.
STR that work reliably for me in Fenix Nightly (101.0a1 #201587625):
- Open Home Screen
- Tap on wikipedia shortuct
Expected:
Page loads.
Actual:
Black (sometimes white) screen.
Needs to be repeated few times to trigger the problem. I've also encountered this just following a link.
This started happening at 2022-04-05 based on bug 1692701. It looks like a regression of 1753700, but still needs to be confirmed.
Fenix ticket: https://github.com/mozilla-mobile/fenix/issues/24782
|
|
1,772,597 | 15,926,240 |
+++ This bug was initially created as a clone of Bug #1763874 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
Steps to reproduce:
Run the following test case (possibly not minimal):
```
gczeal(14);
var c = ["a", "b"];
var t = Tuple.from(c);
for (i = 0; i < 3; i++) {
c = ["a", "b"];
t = Tuple.from(c);
gc();
}
```
Actual results:
```
mach jit-test # test file...
[...]
Assertion failure: result.tenuredBytes <= previousGC.nurseryUsedBytes, at /home/tjc/gecko-fork/js/src/gc/Nursery.cpp:1115
```
Expected results:
The test should pass. I'll have a patch for this ready next week.
The GC has an implicit assumption that only arrays can have fixed elements. Tuples also have fixed elements, but were being treated as if they don't because the code checks whether an object's class is `ArrayObject` or `TypedArrayProject` as a proxy for checking if it has fixed elements. This is related to Bug 1763874 -- but that wasn't a complete fix, because the code that promotes objects to the tenured heap still had the wrong assumption baked in.
So why didn't the test for Bug 1763874 expose this bug? Inexplicably, this assertion failure didn't appear until I integrated the following patch into my working branch: https://hg.mozilla.org/mozilla-unified/rev/516249a8f5c5 . This patch adds a new global function to `TestingFunctions.cpp`. That was how I found the bug, but through experimentation I determined that commenting out *any* function in `TestingFunctions.cpp` would mask the bug; it could also be triggered by adding several global functions to the test case itself. My guess is that when the global object has more than a certain number of properties (I noticed that the bug is triggered when the global object has exactly 511 dynamic slots, and isn't triggered when it has fewer than 511 dynamic slots), allocation behavior changes somehow and the tenured / nursery sizes change so that the assertion starts failing.
I think that suggests that the assertion (this one: https://searchfox.org/mozilla-central/source/js/src/gc/Nursery.cpp#1115 ) needs to be made stricter and/or there's another bug, but this is all I know for now.
|
|
1,773,025 | 15,931,186 |
**Affected versions**
* Fx 102.0b4
* Fx 103.0a1
**Affected platforms**
* Windows 10
* Ubuntu 20.04
* macOS
**Steps to reproduce**
1. Launch Firefox.
2. Navigate to [Reddit](www.reddit.com) and click on a post from the page.
3. Open a new tab and close the previously accessed page from step 2.
4. Type 'redd' in the address bar and choose the reddit post from the Firefox Suggest section. (at this point the adaptive history for 'redd' is created).
5. Bookmark the page.
6. Open a new tab and close the previously accessed page from step 4.
7. Open history (either library or sidebar) and use "Forget about this site" to remove the reddit post entry from history.
8. Delete the bookmark from the bookmark toolbar.
**Expected result**
* No adaptive history for autofil remains (the autofill for 'redd' no longer exists).
* No records exist when checked for in the browser console.
**Actual result**
* Adaptive history autofill triggers briefly (flickers) for every letter of the word 'redd' that is typed in the address bar.
**Regression range**
* This is not a regression.
**Additional notes**
* This seems to be because of the weird interaction between 'Forget about this site' functionality and bookmarking.
What I mean by this is that:
- if bookmark is removed first, then the forget about this site is used, there is no adaptive history.
- if the user just DELETES the history entry and then removes the bookmark, no adaptive history entry remains.
- if an adaptive autofill entry is done on a record that exists only in history and the 'forget about this site' functionality is used on the history entry, the adaptive autofill entry is removed.
- if an adaptive autofill entry is done on a record that exists only in bookmarks and then the user deletes the bookmark, the adaptive autofill entry is removed.
|
|
1,773,212 | 15,932,728 |
Created attachment 9280192
Bildschirmfoto 2022-06-08 um 09.13.58.pdf
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:101.0) Gecko/20100101 Firefox/101.0
Steps to reproduce:
I try it with a new Profile, but still the same
Actual results:
see screenshot
Expected results:
in about:preferences#general and the other pref-pages the resizing is working
|
|
1,774,220 | 15,942,773 |
Created attachment 9281216
rec of the issue.gif
**[Notes]:**
- This issue is not reproducible on the "Control" branch of the experiment.
**[Affected versions]:**
- Firefox Beta 102.0b7 - Build ID: 20220612185901
**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- "nimbus.debug" pref set to "true".
- Have the browser's "Dark" theme enabled from "about:addons>Themes" page.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to the "about:studies?optin_slug=about-welcome-mobile-download&optin_branch=treatment-b&optin_collection=nimbus-preview" URL.
3. Restart the browser and navigate to the "about:welcome" page.
4. Navigate to the "Theme" screen and observe the primary button's label.
**[Expected result]:**
- The "Done" label is displayed.
**[Actual result]:**
- The "Save theme" label is displayed instead.
**[Additional Notes]:**
- This issue is reproducible on both "treatment" branches of the experiment.
- Attached a screen recording of the issue.
|
|
1,774,885 | 15,947,935 |
Created attachment 9281873
screengrab
When typing "red", the URL bar will now autocomplete as _red_`.reddit.com/r/linux`. This doesn't really make sense. The URL in the dropdown is still correct. I think I've seen this bug for the first time this week (using Nightly).
|
|
1,775,071 | 15,950,905 |
Perfherder has detected a devtools performance regression from push [b510338a2eb9405c76ea49a2b04fd0679a779d02](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=b510338a2eb9405c76ea49a2b04fd0679a779d02). As author of one of the patches included in that push, we need your help to address this regression.
### Regressions:
| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**|
|--|--|--|--|--|
| [17%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194389,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-symbol | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 52.58 -> 61.32 |
| [14%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194410,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-symbol | windows10-64-shippable-qr | e10s fission stylo webrender | 53.76 -> 61.34 |
| [13%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194387,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-bool | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 40.58 -> 45.83 |
| [11%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4209633,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-symbol | linux1804-64-shippable-qr | e10s fission stylo webrender | 54.58 -> 60.72 |
| [11%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194391,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-typedarray | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 83.86 -> 93.14 |
| [11%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194385,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-undefined | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 42.96 -> 47.55 |
| [10%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194408,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-bool | windows10-64-shippable-qr | e10s fission stylo webrender | 40.89 -> 45.13 |
| [10%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194412,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-typedarray | windows10-64-shippable-qr | e10s fission stylo webrender | 85.56 -> 94.14 |
| [10%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194401,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-longstring | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 53.71 -> 59.06 |
| [10%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194382,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-number | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 55.10 -> 60.39 |
|...|...|...|...|...|
| [3%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4209686,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-nodelist | macosx1015-64-shippable-qr | e10s fission stylo webrender-sw | 250.66 -> 258.09 |
| [3%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4194396,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.log-in-loop-content-process-nodelist | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 259.43 -> 266.37 |
| [2%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4087099,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.streamlog | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 1,647.88 -> 1,684.43 |
| [2%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,3871677,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.streamlog | windows10-64-shippable-qr | e10s fission stylo webrender | 1,646.82 -> 1,680.34 |
| [2%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4087104,1,12) | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) console.typing | windows10-64-shippable-qr | e10s fission stylo webrender-sw | 373.71 -> 381.18 |
Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=34482), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
|
|
1,776,262 | 15,956,796 |
My problem is the *opposite* of https://bugzilla.mozilla.org/show_bug.cgi?id=1760910 . Basically, I scroll up in the JavaScript console to inspect data, but the console keeps forcibly scrolling to the bottom.
I think I've found *why* it does that. I see this happening when having the console pulled up in the virtual tabletop "Foundry VTT", which does a periodic (every second XHR to /api/status). Every time the XHR happens, the console is forced to the bottom.
*However*, this only happens when the XHR are filtered away using the selector thingy at the top-right of the dev tools. Basically, it seems that when the XHR are not filtered away, the console correctly checks that, yes, the user manually scrolled to up, so we don't want to force them down; but when the XHR are filtered away, that check doesn't happen, so the console is forced to the bottom even though the new message isn't even shown.
Unfortunately, I don't think I can offer an easy way for someone else to reproduce this issue, save using Foundry VTT itself.
|
|
1,776,763 | 15,961,841 |
# Environment
- Firefox 103 Nightly, build id 20220627075547
- https://hg.mozilla.org/mozilla-central/rev/a66dcaea419641c5483a43aa7f577b70908d147f
- macOS Monterey 12.4, Intel
# Steps to reproduce
1. Launch Firefox.
2. Try to open a new window from "New Window" or "New Private Window" in macOS' Dock's context menu.
# Actual Result
- Take a long time (10sec~1min) to open a new window.
- This is not reproducible if I try to open a new window from:
- menubar -> "File" -> "New Window" or "New Private Window".
- "New Window" or "New Private Window" from hamburger menu in the browser window.
# Note
I feel this bug did not happen in 10 or more days ago.
|
|
1,785,987 | 16,037,404 |
Created attachment 9290602
downloadLink_Focus.gif
**[Affected versions]:**
- Firefox Nightly 105.0a1 (Build ID: 20220818214910)
**[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 Mobile Cross-Promo screen is displayed.
3. Click the “send yourself a download link” link.
4. Observe what happens.
**[Expected result]:**
- The Download page is opened in a new tab, and the focus remains on the “about:welcome” page.
**[Actual result]:**
- The Download page is opened in a new tab, and the focus switches to this page.
**[Notes]:**
- This issue is specific only for new users.
- Attached is a screen recording of the issue.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.