Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34949 - [couchdb] crash with js-17.0.0-1, downgrade required
Attached to Project:
Community Packages
Opened by Simon Lipp (Sloonz) - Thursday, 25 April 2013, 12:53 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 24 June 2013, 09:52 GMT
Opened by Simon Lipp (Sloonz) - Thursday, 25 April 2013, 12:53 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 24 June 2013, 09:52 GMT
|
DetailsUpgrading the js package from 1.8.5-3 to 17.0.0-1 causes CouchDB to crash when using filters with javascript, returning this error in the logs :
** Reason for termination == ** {bad_return_value,{os_process_error,{exit_status,127}}} Downgrading js fixes the crash. The most likely explanation is that /usr/bin/js doesn’t exists anymore in 17.0.0-1 (it’s /usr/bin/js17). Not sure if it should be labeled as a js bug or couchdb bug, feel free to ask me to open a bug on the archlinux tracker. |
This task depends upon
The problem looks to be dependency in the couchdb js file (/usr/bin/couchjs) to libmozjs185.so.1.0.0, which is part of js185.
I would presume the problem would be fixed in the package by changing the dependency for js to js185.
I haven't done a custom couchdb build in a while, but I do believe it would work if compiled against the current js 17. However, it does not appear to be a path to stability, or something that one would push out to the main couchdb package:
Versions of SpiderMonkey after the js185-1.0.0 release remove the optional
enforcement of preventing anonymous functions in a statement context. This
will most likely break your existing JavaScript code as well as render all
example code invalid.