Brian May <[EMAIL PROTECTED]> writes:
> Jeremy Maitin-Shepard wrote:
>> You didn't happen to get a stack trace in the terminal, did you? I
>> tried to track down the problem from that brief description alone, but I
>> was not able to. A stack trace would make it much easier.
>>
>> As I said, if you are running on Linux, the stack trace will be printed
>> to the terminal in which you invoke conkeror. On Windows, you need to
>> invoke Conkeror with the -console command-line option in order to have
>> it open a terminal, in which the stack trace will be visible
> Speaking of stack traces, Conkeror crashed on me today (everything froze
> - I was browsing HP and Dell websites at the time), and it looks like I
> do have a stack trace (I don't know if this is the same issue or not). I
> suspect it isn't going to help. However before I close the terminal
> window, here it is:
Thanks. I suspect that the ultimate crash is unrelated to those error
messages. Actually, all of those error messages that you see would
previously have just shown up in the JavaScript console, but a recent
change that I checked in by mistake (a mistake because the output format
is not completely set, and error caused by content JavaScript are not
yet always filtered out) now prints them to the terminal.
> [...]
> Console error: [JavaScript Error: "uncaught exception: [Exception...
> "Component
> returned failure code: 0x80004005 (NS_ERROR_FAILURE)
> [nsIWebNavigation.loadURI]"
> nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
> chrome://conkeror-modules/content/load-spec.js :: apply_load_spec :: line 220"
> data: no]"]
> Category: chrome javascript
This error should be handled more gracefully, but this is probably just
due to trying to load an invalid URL.
> Console error: [JavaScript Error: "already executing generator g.send" {file:
> "chrome://conkeror-modules/content/coroutine.js" line: 100}]
> Category: XPConnect JavaScript
> Console error: [JavaScript Error: "already executing generator g.send" {file:
> "chrome://conkeror-modules/content/coroutine.js" line: 100}]
> Category: XPConnect JavaScript
> Console error: [JavaScript Error: "already executing generator g.send" {file:
> "chrome://conkeror-modules/content/coroutine.js" line: 100}]
> Category: XPConnect JavaScript
> Console error: [JavaScript Error: "already executing generator g.send" {file:
> "chrome://conkeror-modules/content/coroutine.js" line: 100}]
> Category: XPConnect JavaScript
> Console error: [JavaScript Error: "already executing generator g.send" {file:
> "chrome://conkeror-modules/content/coroutine.js" line: 100}]
> Category: XPConnect JavaScript
These errors are all real errors that reflect a programming error. I
have some idea of what is happening, but because there is no stack trace
I don't have a good idea of _where_ this error is being caused. If you
happen to have any ideas about what you were doing when this error
occurred, or (better yet) can reliably reproduce it, let me know.
> Console error: [JavaScript Warning: "Use of captureEvents() is deprecated, see
> bug 330494." {file:
> "http://www.via.com.tw/en/initiatives/empowered/pc2500_mainboard/index.jsp";
> line: 0}]
> Category: DOM Events
> Console error: [JavaScript Error: "handler is undefined" {file:
> "http://www.zonbu.com/include/js/prototype.js"; line: 3842}]
> Category: XPConnect JavaScript
These two errors are caused by the content page and therefore can be ignored.
> *** glibc detected *** /home/brian/tmp/xulrunner/xulrunner-bin: double free or
> corruption (fasttop): 0x093841e8 ***
This actual crash may likely not be a problem in Conkeror per se, but
rather just a problem in xulrunner that may be fixed by upgrading to a
later version. In my experience, plugins also tend to cause crashes.
--
Jeremy Maitin-Shepard
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
