Closed Bug 833831 Opened 12 years ago Closed 12 years ago

bogus spike in Flash crash @ NP_Shutdown since January 22, 14H UTC

Categories

(Firefox for Android Graveyard :: Plugins, defect)

ARM
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, topcrash, Whiteboard: [native-crash])

Crash Data

It has spiked across all versions since January 22 at 14H UTC. It's currently #10 top crasher in 18.0, #4 in 19.0b2, #12 in 20.0a2 and 21.0a1. Signature NP_Shutdown More Reports Search UUID dada0b45-e3f3-46de-b1ec-3dfc52130123 Date Processed 2013-01-23 14:33:06 Uptime 320 Last Crash 5.4 minutes before submission Install Age 5.3 days since version was first installed. Install Time 2013-01-18 08:04:27 Product FennecAndroid Version 21.0a1 Build ID 20130117030933 Release Channel nightly OS Android OS Version 0.0.0 Linux 2.6.35-palm-tenderloin #1 SMP PREEMPT Sun Dec 16 18:30:52 PST 2012 armv7l hp/hp_tenderloin/tenderloin:4.0.4/IMM76I/330937:user/release-keys Build Architecture arm Build Architecture Info Crash Reason SIGSEGV Crash Address 0x0 App Notes AdapterDescription: 'Qualcomm -- Adreno (TM) 220 -- OpenGL ES 2.0 2131267 -- Model: cm_tenderloin, Product: touchpad, Manufacturer: unknown, Hardware: tenderloin' EGL? EGL+ GL Context? GL Context+ GL Layers? GL Layers+ unknown cm_tenderloin hp/hp_tenderloin/tenderloin:4.0.4/IMM76I/330937:user/release-keys Processor Notes sp-processor10.phx1.mozilla.com_16521:2008; exploitablity tool: ERROR: unable to analyze dump EMCheckCompatibility True Adapter Vendor ID Qualcomm Adapter Device ID Adreno (TM) 220 Device unknown cm_tenderloin Android API Version 15 (REL) Android CPU ABI armeabi-v7a Frame Module Signature Source 0 libc.so libc.so@0xddf0 1 libflashplayer.so NP_Shutdown 2 @0xffffffff 3 libflashplayer.so NP_Shutdown 4 libflashplayer.so NP_Shutdown More reports at: https://crash-stats.mozilla.com/report/list?signature=NP_Shutdown https://crash-stats.mozilla.com/report/list?signature=%400x0%20|%20NP_Shutdown
Assignee: nobody → snorp
Kairo, can you please help with URLS or any device correlation here ?
Flags: needinfo?(kairo)
I don't think this bug is useful till bug 833853 is fixed. That should allow breaking down the crashes listed into individual crashes.
This bug is invalid because bug 833853 is changing this signature, converting it to different signatures, and we'll reprocess all those crashes so this will go away completely. Basically, all Android Flash crashes come up with this sig right now.
Assignee: snorp → nobody
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(kairo)
Keywords: needURLs, topcrash
Resolution: --- → INVALID
As a note, bug 834007 is doing the reprocessing mentioned above.
Depends on: 834007, 833853
It's still applicable for stack traces with only one Flash frame such as: Frame Module Signature Source 0 libc.so libc.so@0x12160 1 libc.so libc.so@0x12e52 2 libc.so libc.so@0x12ea2 3 libflashplayer.so NP_Shutdown
Status: RESOLVED → REOPENED
Keywords: topcrash
Resolution: INVALID → ---
Summary: spike in Flash crash @ NP_Shutdown since January 22, 14H UTC → Flash crash @ NP_Shutdown
Let's add crash signatures containing only NP_Shutdown, that is pure Flash crashes.
Crash Signature: [@ NP_Shutdown] [@ @0x0 | NP_Shutdown] → [@ NP_Shutdown] [@ @0x0 | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown] [@ @0x0 | NP_Shutdown | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown | NP_Shutdown | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown | NP_Shutdow…
And it's still bogus and useless.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → INVALID
Summary: Flash crash @ NP_Shutdown → bogus spike in Flash crash @ NP_Shutdown since January 22, 14H UTC
And if anything, please file new bugs on specific problems, we have nothing in our hands to do anything about a generic collector of all Android Flash crash, as this useless collection of signatures would produce. Adobe is not caring about those as Android Flash has been discontinued and we have no way of dealing with them unless we know any specifics.
Crash Signature: [@ NP_Shutdown] [@ @0x0 | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown] [@ @0x0 | NP_Shutdown | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown | NP_Shutdown | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown | NP_Shutdow… → [@ NP_Shutdown] [@ @0x0 | NP_Shutdown]
Crash Signature: [@ NP_Shutdown] [@ @0x0 | NP_Shutdown] → [@ NP_Shutdown] [@ @0x0 | NP_Shutdown] [@ NP_Shutdown | NP_Shutdown ] [@ NP_Shutdown | NP_Shutdown | NP_Shutdown ] [@ NP_Shutdown | NP_Shutdown | NP_Shutdown | NP_Shutdown | NP_Shutdown | NP_Shutdown ]
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.