Closed Bug 720615 Opened 14 years ago Closed 13 years ago

Clicking on More Reports leads to an Error

Categories

(Socorro :: Webapp, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: nhirata, Unassigned)

Details

1. go to https://crash-stats.mozilla.com/report/index/9fdce34a-942b-4a13-9e13-261342111227 2. click on More Reports (listed in the Signature field) Expected: no error Actual: Error. Most likely due to the long signature name.
(In reply to Naoki Hirata :nhirata from comment #0) > 1. go to > https://crash-stats.mozilla.com/report/index/9fdce34a-942b-4a13-9e13- > 261342111227 this crash has aged off the system. do you see this with other signatures?
Flags: needinfo?(nhirata.bugzilla)
(In reply to Naoki Hirata :nhirata from comment #0) > 2. click on More Reports (listed in the Signature field) Hrm, would have been helpful to paste what URL that leads you to, as now, with the crash gone from our data, this bug is basically un-actionable and un-QA-able. :(
I currently don't see it in any signature that I see. I can't recall which crash signature this was. I'm guessing it was a FennecAndroid Java crash... having said that I can't see to find a signature name long enough. https://crash-stats.mozilla.com/report/list?signature=java.lang.ClassCastException%3A+android.os.BinderProxy+cannot+be+cast+to+org.mozilla.gecko.NotificationService%24NotificationBinder+at+org.mozilla.gecko.NotificationServiceClient%24NotificationServiceConnection.onServiceConnected%28NotificationServiceClient.java%29 is pretty long yet, it can still find it without errors. Might as well close this off as WFM until we can find another signature that causes the same issue is my thought. At least I know for the future to try to capture the URL.
Flags: needinfo?(nhirata.bugzilla)
Let's mark WFM based on comment #3. If something like that comes up again with the django UI, we should get a new bug on file.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.