Comment by chriswarbo | Hacker News Reader

Comment by chriswarbo | Hacker News Reader

Parent Full thread

Looks like a cool project, but I can't scroll very far down the site before my browser crashes. I've reproduced this several times, here's the terminal output if it helps:

    $ conkeror https://alpha.trycarbide.com
    ......
    JavaScript strict warning: https://alpha.trycarbide.com/, line 603: SyntaxError: test for equality (==) mistyped as assignment (=)?
    JavaScript strict warning: https://alpha.trycarbide.com/, line 604: SyntaxError: test for equality (==) mistyped as assignment (=)?
    JavaScript strict warning: https://alpha.trycarbide.com/, line 605: SyntaxError: test for equality (==) mistyped as assignment (=)?
    JavaScript strict warning: https://alpha.trycarbide.com/, line 606: SyntaxError: test for equality (==) mistyped as assignment (=)?
    JavaScript strict warning: https://eponymous-labs.github.io/carbide-splash/static/main.js, line 162: SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function
    JavaScript strict warning: https://eponymous-labs.github.io/carbide-splash/static/main.js, line 201: ReferenceError: assignment to undeclared variable diff
    Console error: [JavaScript Warning: "window.controllers is deprecated. Do not use it for UA detection." {file: "chrome://conkeror/content/window.js" line: 331}]
      Category: DOM Core
    Segmentation fault

Well, if the browser segfaulted, it is not the page's fault. It is the browser's. No ifs or buts.

I'd suggest enabling core dumps and sending those to the Conkeror team, assuming there's no bug filed for that.

I know how this line of defense plays out with my customers if their customers' browsers segfault on a page I wrote...

I fix the page ASAP to prevent the segfault and then file a bug to the browser developers. If I don't, I lose the customer and somebody else will fix the page anyway, maybe not filing the bug because it doesn't make money.

Just how do you "fix a segfault" in your page? Do you immediately replicate the user's exact computing environment, all down to the specific operating system and perhaps browser plugins which might contribute, install a specific version of the this obscure browser (Conkeror?) with debug symbols, fire up GDB and understand why the complex C++ crashed based on the core dump?

That seems like an unlikely amount of effort. IME If you have some "enterprise" tool with enterprise clients, there's typically going to be a list of browsers which are supported and tested by QA.

Having been in similar situations, I think he means that he does indeed replicate the bug (which isn't usually as bad as you make it sound) and then write different code that doesn't trigger that bug in the browser.

It isn't always possible, and in that case we do blame the browser in the end, but it usually is possible to work around it. It's ugly, but it's necessary to keep your customers happy.

I'd rewrite the page in a way that it doesn't trigger the bug. Trial and error, not the nicest of the days.

For one customer in a sea of thousands doesn't seem too worth it in my opinion

My customer is the one who runs the site, not the ones who browse it.

Also has problems with Safari on iOS. After a short while i get the "page caused a problem and was reloaded" message.

Freezes the browser here, mobile Firefox

Reply on news.ycombinator.com