Closed Bug 596881 Opened 15 years ago Closed 14 years ago

Crash signature links give "No Data" messages ; have no data

Categories

(Socorro :: General, task)

task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stephend, Assigned: rhelmer)

References

()

Details

STR: 1. Load on http://crash-stats.stage.mozilla.com/topcrasher/bydomain/Firefox/4.0b3pre 2. Click on "Expand 'tendollarclick'" 3. Click on one of the sub-links 4. Click on a crash signature, such as http://crash-stats.stage.mozilla.com/report/list?product=Firefox&version=Firefox%3A4.0b3pre&date=&range_value=1&range_unit=weeks&query_search=signature&query=@bc101380&query_type=exact&do_query=1&signature=@bc101380 Expected Results: Query for that signature loads Actual Results: "No Data This query or location currently has no data."
Assignee: nobody → ozten.bugs
The crash signatures in stage are based on corrupt symbol tables, this was fixed in production only in bug 596766. Fixing this is dependent on the backend data in stage being good, not sure if this is going to be cleaned out in the same way or just reloaded entirely. Leaving this open for right now. Stephen, can you please try to reproduce in production? Austin and I have been unable to repro in prod so far.
Status: NEW → ASSIGNED
I get an "Unable to Complete Request" when trying to look at trunk crash data such as http://crash-stats.mozilla.com/report/index/e59b8c97-5016-4902-a10e-2e7232100916 and http://crash-stats.mozilla.com/report/index/502fdade-4665-4bbe-b631-2fb3b2100916, not sure if this is the same bug or whether I should file a new one?
rhelmer: still can reproduce on prod: 1. Load http://crash-stats.mozilla.com/topcrasher/bydomain/Firefox/4.0b3pre 2. Expand "Expand me.zing.vn" and its sub-entry (may take a few tries -- this is a 1.7 bug we fixed in 1.8) 3. Click on the resulting xul.dll@0x1a5fc0 entry: http://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox%3A4.0b3pre&date=&range_value=1&range_unit=weeks&query_search=signature&query=xul.dll@0x1a5fc0&query_type=exact&do_query=1&signature=xul.dll@0x1a5fc0 You'll get the same error as in comment 0 (returns 200 OK).
(In reply to comment #2) > I get an "Unable to Complete Request" when trying to look at trunk crash data > such as > http://crash-stats.mozilla.com/report/index/e59b8c97-5016-4902-a10e-2e7232100916 > and > http://crash-stats.mozilla.com/report/index/502fdade-4665-4bbe-b631-2fb3b2100916, > not sure if this is the same bug or whether I should file a new one? I think this is bug 597121
(In reply to comment #3) > rhelmer: still can reproduce on prod: > > 1. Load http://crash-stats.mozilla.com/topcrasher/bydomain/Firefox/4.0b3pre > 2. Expand "Expand me.zing.vn" and its sub-entry (may take a few tries -- this > is a 1.7 bug we fixed in 1.8) > 3. Click on the resulting xul.dll@0x1a5fc0 entry: > > http://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox%3A4.0b3pre&date=&range_value=1&range_unit=weeks&query_search=signature&query=xul.dll@0x1a5fc0&query_type=exact&do_query=1&signature=xul.dll@0x1a5fc0 > > You'll get the same error as in comment 0 (returns 200 OK). We actually rolled back to 1.7, it's possible that we need to do something like bug 596766 again. I'm following up now, thanks!
Assignee: ozten.bugs → robert
(In reply to comment #6) > I see this in prod too: Sorry this should read "I see this in stage too"
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #6) > > > I see this in prod too: > > > http://crash-stats.stage.mozilla.com/topcrasher/bydomain/Firefox/4.0b3pre > > > "hackiswack.com" > > > http://crash-stats.stage.mozilla.com/report/list?product=Firefox&version=Firefox%3A4.0b3pre&date=&range_value=1&range_unit=weeks&query_search=signature&query=@f3f0fa&query_type=exact&do_query=1&signature=@f3f0fa > > > > Isn't this just bug 569178? The only crash for that signature happened more > > than 1 week ago (3 Sep). > > Probably; Rob? Yes I think so too, I don't see any examples that are within the last week. Let's follow up in bug 569178. Please reopen if you see any examples to the contrary.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Verified; this seems fine.
Status: RESOLVED → VERIFIED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.