Opened 13 years ago
Closed 12 years ago
#2492 closed defect (fixed)
browse segfaults on maps.google.com javascript execution
Reported by: | quozl | Owned by: | lucian |
---|---|---|---|
Priority: | Low | Milestone: | Unspecified |
Component: | Browse | Version: | Git as of bugdate |
Severity: | Critical | Keywords: | |
Cc: | Distribution/OS: | ||
Bug Status: | New |
Description
Start Browse, click on URL text entry, type maps.google.com, press enter.
Browse will terminate.
Browse should not terminate.
Affects Browse-108 on XO-1.5 OLPC OS 10.1.2 os852, XO-1 with Browse-101 and Browse-115.
Reported by Esteban Bordon, reproduced by James Cameron.
Attachments (2)
Change History (6)
Changed 13 years ago by quozl
comment:1 Changed 13 years ago by sascha_silbe
- Priority changed from Unspecified by Maintainer to Low
- Severity changed from Minor to Critical
- Version changed from Unspecified to Git as of bugdate
Reproduced on Debian Squeeze.
The crash happens deep in C code, as part of some event processing. Even if Browse did something wrong that triggers the crash, it's clearly the fault of some other component. Not sure exactly which component is to blame (candidates are at least python-xpcom, libmozjs and xulrunner), though my first guess would be python-xpcom.
comment:2 Changed 13 years ago by lucian
Perhaps it would be useful to try and reproduce the bug with something like http://wiki.laptop.org/go/Sugar_Code_Snippets#WebView, perhaps there is indeed something that Browse in particular does to trigger this bug, in which case there could be a workaround.
comment:3 Changed 13 years ago by quozl
Reproduced as suggested using the WebView code snippet. The stack trace looks identical. Therefore there is nothing in Browse itself that is triggering this.
Changed 13 years ago by quozl
gdb backtrace showing point of failure, using webview instead of browse
comment:4 Changed 12 years ago by RafaelOrtiz
- Resolution set to fixed
- Status changed from new to closed
Not being able to reproduce anymore on browse git. closing for now, re opening if happens agains.
gdb backtrace showing point of failure