css_to_xpath mem leak with non ascii selectors

Bug #754636 reported by Kovid Goyal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxml
Won't Fix
Undecided
Unassigned

Bug Description

python -c "from lxml.cssselect import css_to_xpath; print css_to_xpath(u'.test\u201d')"

This causes a massive memory leak on windows and OSX but correctly raises an exception on linux.

Windows versions:
Python : sys.version_info(major=2, minor=7, micro=1, releaselevel='final', serial=0)
lxml.etree : (2, 3, 0, 0)
libxml used : (2, 7, 7)
libxml compiled : (2, 7, 7)
libxslt used : (1, 1, 26)
libxslt compiled : (1, 1, 26)

This is using the lxml package from PyPI

Revision history for this message
scoder (scoder) wrote :

I wouldn't know why this should be system specific. In any case, note that cssselect is currently becoming its own project, so this won't be fixed in lxml anymore. lxml will start to use the separate cssselect in the future.

See

https://github.com/SimonSapin/cssselect

Changed in lxml:
status: New → Won't Fix
Revision history for this message
scoder (scoder) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.