[Firefox Desktop] Issues found: November 9th to November 13th

[Andrei Vaida]

Hi everyone,

Here's the list of new issues found and filed by the Desktop Manual QA 
team last week (Week 46: November 09 - November 13).


Additional details on the team's priorities last week, as well as the 
plans for the current week are available at:


   https://public.etherpad-mozilla.org/p/DesktopManualQAWeeklyStatus



*RELEASE CHANNEL*
none

*BETA CHANNEL*
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
NORMAL  1223328 
[XP] Artifacts present when changing youtube video quality
NEW 
NO  NOBODY
NORMAL  1223391 
	[Linux] Audio jumps when I'm right clicking in different places on the 
time bar

NEW 
YES NOBODY
NORMAL  1224550 
Glitches when resizing firefox width on unsplash.com
NEW 
NO  NOBODY
NORMAL  1224552 
	Awesome bar with search suggestions enabled flickers with some search 
engines

NEW 
NO  NOBODY


*AURORA CHANNEL*
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
NORMAL  1224553 
	The stats are displayed for one second when opening a picture from 
unsplash.com

NEW 
NO  NOBODY


*NIGHTLY CHANNEL*
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
CRITICAL1222970 
crash in shutdownhang | libsystem_kernel.dylib@0x16f5e
NEW 
YES NOBODY
MINOR   1223827 
The results of the Snapshots are not centered on the horizontal
NEW 
NO  NOBODY


*ESR CHANNEL*
none


Regards,
Andrei.
Andrei Vaida| QC Team Lead

SOFTVISION | 57 Republicii Street, 400489 Cluj-Napoca, Romania
Email: andrei.va...@softvision.ro  | 
Web: www.softvision.ro 


The content of this communication is classified as SOFTVISION 
Confidential and Proprietary Information.



___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

FYI: updating yasm on build machines

[Chris Peterson]

mozilla-build uses yasm 1.3, but the build machines still use yasm 1.1, 
which is at least three years out of date. Bug 1224408 will update the 
build machines to use yasm 1.3.


There are no expected problems because local builds using mozilla-build 
tools already use 1.3. mozilla-central has yasm code in libvpx, 
spidermonkey, skia, cairo, nss, libjpeg, and webrtc.

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

New memory profiling tool available

[陳侃如]

Hi!

This is an on going project that recently moved into a usable state. The
objective is to let developers profile their website or apps to analyze
their memory allocation characteristics. For example it could be used to
find memory allocation hot spots that might give memory pressure to
other apps on the system.

The profiler is designed at the very beginning to support not only
JavaScript but also native codes. Naturally, not only JavaScript objects
but also native allocations are tracked.

It samples memory allocation based on accumulated allocation sizes so it
could detect both rapid allocations and large allocations. Each
allocation sampled has size and stack trace recorded so these sampled
events can be used to approximate the full history of allocations
afterwards. It also impose very low overhead on the system being
profiled.

Currently the gecko support has been landed on mozilla-central and
enabled by default. The ability to sample native allocations is enabled
when replace-malloc is enabled, which is default on Nightly.

The user interface is developed as an devtools add-on. Once installed it
could be accessed from developer toolbar or WebIDE.
Here are instructions for installing and using the Memory Profiler add-on:
https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Memory_Profiler

We also plan to work on a command line interface for scripting and
custom post-processing.

Here is the project page if you are interested and want to contribute:
https://wiki.mozilla.org/MemoryProfiler

Please try it out and file bugs in the "Core" product and "Gecko
Profiler" component! We want this to be a useful tool for _you_!

Cheers,
Kanru
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Error of OS X build (c-c TB)

[ISHIKAWA,chiaki]

On 2015/11/16 17:03, ISHIKAWA,chiaki wrote:

On 2015/11/15 14:28, Xidorn Quan wrote:
On Sun, Nov 15, 2015 at 1:05 PM, ISHIKAWA,chiaki 
 wrote:

On 2015/11/14 12:31, Xidorn Quan wrote:

Have you checked your log here:

https://treeherder.mozilla.org/logviewer.html#?job_id=11934=try-comm-central 



- Xidorn


Yes, I have looked at it.

The information there is sparse. The error indicates there is ambiguity
resolving TextArea symbol.

The information from the log looks fairly enough to me. The content of
AERegistry.h around the location actually has nothing interesting:

struct TextRange {
  SInt32  fStart;
  SInt32  fEnd;
  SInt16  fHiliteStyle;
};
typedef struct TextRangeTextRange;
typedef TextRange * TextRangePtr;
typedef TextRangePtr *  TextRangeHandle;
But, since the same ambiguous error does not occur in linux build,
I can only guess that there are similarly named data type or 
something in
OS X specific headers which is confusing the compiler (clang?), and 
thus
I want to know if someone with OS X developer source files can 
figure this

out.
I am not sure why others don't bump into this issue under OS X.
My patch does NOT touch anything related to "TextArea", etc.

It seems you added some #include which did not exist before which
causes this issue. You may want to reorder the #includes in
nsStreamUtils.cpp to workaround. I don't have particularly good
suggestion here.

- Xidorn


Thank you for your help.

I modified the source so that the include is taken out.

Problem is that although my patches will build linux and Windows 
binaries, but under OS X, there seems to be a configure error, even. 
Now I can't proceed to the compilation stage even. Hmm...


https://treeherder.mozilla.org/#/jobs?repo=try-comm-central=8f2de14e9fd2 




ValueError: Item already in manifest: 
chrome/classic/skin/classic/messenger/addressbook/icons/abcard.png

make[2]: *** [configure] Error 1

1047760 Intermittent build failures with "ccache: failed to create 
/builds/ccache/tmp (No such file or directory)" ("make[3]: *** 
[configure] Error 1", "make[2]: *** [configure] Error 1" or "make: *** 
[configure] Error 1")


make[1]: *** 
[/builds/slave/tb-try-c-cen-m64-d-000/build/objdir-tb/Makefile] Error 
2



The particular error does not seem to be correct. (bug 1047760).



I removed the newly introduced include as suggested AND
after removing the duplication (of two entries)
in theme/osx/jar.mn (this has also been
addressed by a new patch in bugzilla),
I could build C-C TB under OS X on Try Server (!)

https://treeherder.mozilla.org/#/jobs?repo=try-comm-central=c374265b8011

Thank you for your suggestion.

Now, though, the following bug busts testing of all the builds.
It is hard to check the sanity of any patches :-(

*Bug 1224840*  
-mozmill run: Assertion failure: IsOuterWindow(), at 
/builds/slave/tb-c-cen-lx-d-/build/mozilla/dom/base/nsGlobalWindow.cpp:7678


One more to go.

Thank you again.

CI
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Web APIs documentation/dev/evangelism meeting Thursday at 8 AM PST

[Eric Shepherd]

The Web API documentation community meeting, with representatives from
the technical evangelism and the API development teams, will take place
on Thursday at 8 AM Pacific Time (see http://bit.ly/1GghwBR for your
time zone).

Typical meetings include news about recent API development progress and
future development plans, discussions about what the priorities for
documenting and promoting new Web technologies should be, and the status
of ongoing work to document and evangelize these technologies.

We have an agenda, as well as details on how to join, here:

https://public.etherpad-mozilla.org/p/API-docs-meeting-2015-11-19.

If you have topics you wish to discuss, please feel free to add them to
the agenda.

We look forward to seeing you there!

If you have topics you wish to discuss, please feel free to add them to
the agenda. Also, if you're unable to attend but have information or
suggestions related to APIs on the Web, their documentation, and how we
promote these APIs, please add a note or item to the agenda so we can be
sure to address it, even if you're unable to attend.

-- 

Eric Shepherd
Senior Technical Writer
Mozilla 
Blog: http://www.bitstampede.com/
Twitter: http://twitter.com/sheppy
Check my Availability 
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Error of OS X build (c-c TB)

[ISHIKAWA,chiaki]

On 2015/11/15 14:28, Xidorn Quan wrote:

On Sun, Nov 15, 2015 at 1:05 PM, ISHIKAWA,chiaki  wrote:

On 2015/11/14 12:31, Xidorn Quan wrote:

Have you checked your log here:

https://treeherder.mozilla.org/logviewer.html#?job_id=11934=try-comm-central

- Xidorn


Yes, I have looked at it.

The information there is sparse. The error indicates there is ambiguity
resolving TextArea symbol.

The information from the log looks fairly enough to me. The content of
AERegistry.h around the location actually has nothing interesting:

struct TextRange {
  SInt32  fStart;
  SInt32  fEnd;
  SInt16  fHiliteStyle;
};
typedef struct TextRangeTextRange;
typedef TextRange * TextRangePtr;
typedef TextRangePtr *  TextRangeHandle;
But, since the same ambiguous error does not occur in linux build,
I can only guess that there are similarly named data type or something in
OS X specific headers which is confusing the compiler (clang?), and thus
I want to know if someone with OS X developer source files can figure this
out.
I am not sure why others don't bump into this issue under OS X.
My patch does NOT touch anything related to "TextArea", etc.

It seems you added some #include which did not exist before which
causes this issue. You may want to reorder the #includes in
nsStreamUtils.cpp to workaround. I don't have particularly good
suggestion here.

- Xidorn


Thank you for your help.

I modified the source so that the include is taken out.

Problem is that although my patches will build linux and Windows 
binaries, but under OS X, there seems to be a configure error, even. Now 
I can't proceed to the compilation stage even. Hmm...


https://treeherder.mozilla.org/#/jobs?repo=try-comm-central=8f2de14e9fd2


ValueError: Item already in manifest: 
chrome/classic/skin/classic/messenger/addressbook/icons/abcard.png

make[2]: *** [configure] Error 1

1047760 Intermittent build failures with "ccache: failed to create 
/builds/ccache/tmp (No such file or directory)" ("make[3]: *** 
[configure] Error 1", "make[2]: *** [configure] Error 1" or "make: *** 
[configure] Error 1")


make[1]: *** 
[/builds/slave/tb-try-c-cen-m64-d-000/build/objdir-tb/Makefile] 
Error 2



The particular error does not seem to be correct. (bug 1047760).

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform