Closed Bug 662934 Opened 13 years ago Closed 5 years ago

crash [@ libxul.so@0x1133a90][@ neon_composite_over_8888_0565]

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Maemo
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: nhirata, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-ccbb6031-c208-4ff1-889f-604202110605 .
============================================================= 
Frame 	Module 	Signature [Expand] 	Source
0 	libxul.so 	libxul.so@0x1133a90 	
1 		@0x44f26fff 	
2 		@0x44ab8fff 	
3 	libxul.so 	neon_composite_over_8888_0565 	gfx/cairo/libpixman/src/pixman-arm-neon.c:61
4 		@0x44ab8fff 	
5 	libxul.so 	_moz_pixman_image_composite32 	gfx/cairo/libpixman/src/pixman.c:373
6 	libxul.so 	neon_composite_over_8888_8888 	gfx/cairo/libpixman/src/pixman-arm-neon.c:63
7 	libxul.so 	_moz_pixman_image_composite 	gfx/cairo/libpixman/src/pixman.c:921
8 	libxul.so 	_cairo_image_surface_composite 	gfx/cairo/cairo/src/cairo-image-surface.c:1175
9 		@0x44f26fff 	
10 	libxul.so 	neon_composite_src_0565_0565 	gfx/cairo/libpixman/src/pixman-arm-neon.c:41



Not sure if the stack is useful, but it seems as if all the crashes are on the N900 platform.
Crash Signature: [@ libxul.so@0x1133a90]
Seems like this all is happening with 2.6.28.10-power47, which is some unofficial custom built kernel : http://talk.maemo.org/showthread.php?t=71879
Joel and Aki is this the same kernel we use on the automation n900s?
what I see is on android, not maemo.  I am not sure how to determine the kernel version on an android device.
On android there is (was?) pixman neon related bug 623161. Also almost entirely happening with 'cyanogenmod', where the kernel is under suspicion.
Summary: crash [@ libxul.so@0x1133a90] → crash [@ libxul.so@0x1133a90][@ neon_composite_over_8888_0565]
Dupe of bug 623161?
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.