Closed Bug 602053 Opened 15 years ago Closed 14 years ago

Crash [@ mozilla::dom::TabParent::GetWidget]

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Maemo
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: martijn.martijn, Unassigned)

References

()

Details

(Keywords: crash)

Crash Data

I got this crash while carrying out the litmus test mentioned in the url field. This was while trying to zoom in on one of the tabs or something. Unfortunately, I don't have steps to reproduce. This crash occured, using: Mozilla/5.0 (Maemo; Linux armv7l; rv:2.0b7pre) Gecko/20101001 Firefox/4.0b7pre Fennec/4.0b1 http://crash-stats.mozilla.com/report/index/36ceeb8d-709d-4cce-9dd6-33fbb2101005 0 libxul.so nsCOMPtr_base::assign_from_qi nsCOMPtr.cpp:47 1 libxul.so mozilla::dom::TabParent::GetWidget nsCOMPtr.h:595 2 libxul.so mozilla::dom::TabParent::HandleQueryContentEvent dom/ipc/TabParent.cpp:403 3 libxul.so nsEventStateManager::RemoteQueryContentEvent content/events/src/nsEventStateManager.cpp:3291 4 libxul.so nsEventStateManager::PreHandleEvent content/events/src/nsEventStateManager.cpp:1321 5 libxul.so PresShell::HandleEventInternal layout/base/nsPresShell.cpp:6915 6 libxul.so PresShell::HandleEvent layout/base/nsPresShell.cpp:6684 7 libxul.so nsViewManager::HandleEvent view/src/nsViewManager.cpp:1093 8 libxul.so nsViewManager::DispatchEvent view/src/nsViewManager.cpp:1071 9 libxul.so HandleEvent view/src/nsView.cpp:161 10 libxul.so nsWindow::DispatchEvent widget/src/gtk2/nsWindow.cpp:734 11 libxul.so nsGtkIMModule::GetCurrentParagraph widget/src/gtk2/nsGtkIMModule.cpp:1377 12 libxul.so nsGtkIMModule::OnRetrieveSurroundingNative widget/src/gtk2/nsGtkIMModule.cpp:862 13 libxul.so nsGtkIMModule::OnRetrieveSurroundingCallback widget/src/gtk2/nsGtkIMModule.cpp:843
Crash Signature: [@ mozilla::dom::TabParent::GetWidget]
OS: Windows 7 → Maemo
Hardware: x86 → ARM
If this is Maemo only, this can be closed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.