Assertion failure: hasMOVWT(), at ../../../js/src/jit/arm/Assembler-arm.cpp:1494 during M-gl on Android 4.0 Debug

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
5 years ago
5 years ago

People

(Reporter: gbrown, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Reporter)

Comment 1

5 years ago
(Sorry - fat fingers hit Enter too soon!)

This assertion is seen during mochitest-gl when running on Android 4.0 Debug.

https://tbpl.mozilla.org/php/getParsedLog.php?id=30714581&tree=Cedar&full=1#error0

11:59:29     INFO -  11-18 11:59:12.273 I/Gecko   ( 2225): AndroidBridge::GetMimeTypeFromExtensions
11:59:29     INFO -  11-18 11:59:12.273 I/Gecko   ( 2225): AndroidBridge::GetMimeTypeFromExtensions
11:59:29     INFO -  11-18 11:59:12.281 I/Gecko   ( 2225): nsWindow[0x69179000]::Create 0x0 [0 0 0 0]
11:59:29     INFO -  11-18 11:59:12.281 I/Gecko   ( 2225): nsWindow[0x69179000]::Show 0
11:59:29     INFO -  11-18 11:59:12.281 I/Gecko   ( 2225): ++DOMWINDOW == 5 (0x65911bec) [pid = 2225] [serial = 5] [outer = 0x6591092c]
11:59:29     INFO -  11-18 11:59:12.312 I/Gecko   ( 2225): nsWindow[0x68f68000]::Create 0x0 [0 0 0 0]
11:59:29     INFO -  11-18 11:59:12.312 I/Gecko   ( 2225): nsWindow[0x68f68000]::Show 0
11:59:29     INFO -  11-18 11:59:12.320 I/Gecko   ( 2225): WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80520012: file ../../../layout/style/Loader.cpp, line 1999
11:59:29     INFO -  11-18 11:59:12.335 F/MOZ_Assert( 2225): Assertion failure: hasMOVWT(), at ../../../js/src/jit/arm/Assembler-arm.cpp:1494
11:59:29     INFO -  11-18 11:59:12.335 F/libc    ( 2225): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): int mozilla::AndroidBridge::GetScreenDepth()
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetGfxInfoData
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetStaticStringField MODEL
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetStaticStringField PRODUCT
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetStaticStringField MANUFACTURER
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetStaticIntField SDK_INT
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetStaticStringField HARDWARE
11:59:29     INFO -  11-18 11:59:12.382 I/Gecko   ( 2225): AndroidBridge::GetStaticStringField RELEASE
Summary: Assertion failure: hasMOVWT(), at ../../../js/src/jit/arm/Assembler-arm.cpp:1494 during → Assertion failure: hasMOVWT(), at ../../../js/src/jit/arm/Assembler-arm.cpp:1494 during M-gl on Android 4.0 Debug
Marty, do you know what's going on?
Flags: needinfo?(mrosenberg)
Geoff, Marty needs STR. Running mochitest-gl locally works fine for him
Flags: needinfo?(gbrown)
(Reporter)

Comment 4

5 years ago
Actually, I don't see this on Cedar now either. On Cedar, mochitest-gl is crashing -- bug 960378. This assertion may be masked by the crash (or it may be resolved).
Flags: needinfo?(gbrown)
(Reporter)

Comment 5

5 years ago
I noticed some confusion on irc yesterday and meant to clarify: This bug is only about Android 4.0 *Debug*, which only runs on Cedar currently. We want to get all Android 4.0 Debug tests running green on Cedar so that they can be run on all trunk trees.
(In reply to Geoff Brown [:gbrown] from comment #4)
> Actually, I don't see this on Cedar now either. On Cedar, mochitest-gl is
> crashing -- bug 960378. This assertion may be masked by the crash (or it may
> be resolved).

so... WFM?
(Reporter)

Comment 7

5 years ago
I checked with mjrosenb on irc -- we decided to keep this open until bug 960378 is resolved.
Depends on: 960378
(Reporter)

Comment 8

5 years ago
Bug 960378 is resolved and there is still no sign of this failure in recent tests on Cedar.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(mrosenberg)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.