Segmentation fault while using matcher #587

Activity

1. honnibal

   added a commit that references this issue on Oct 28, 2016

   Test Issue #587: Matcher segfaults on particular input

   782e481
2. honnibal

   added

   bugBugs and behaviour differing from documentationBugs and behaviour differing from documentation

   on Oct 28, 2016
3. honnibal

   added a commit that references this issue on Oct 28, 2016

   Fix Issue #587: Segfault in Matcher, due to simple error in the state…

   ...

   d563f1e
4. honnibal commented on Oct 28, 2016

   

   honnibal

   on Oct 28, 2016

   Member

   More actions

   Hm, was silently ignoring an error condition.

   Fixed now, but looking at this, I doubt this will be the last error. Hopefully they should report more cleanly now though.
5. honnibal

   closed this as completedon Oct 28, 2016
6. sadovnychyi commented on Oct 28, 2016

   

   sadovnychyi

   on Oct 28, 2016

   ContributorAuthor

   More actions

   Thanks!

   Traceback (most recent call last):
     File "word2vec/matcher.py", line 118, in <module>
       matches = matcher(doc)
     File "spacy/matcher.pyx", line 315, in spacy.matcher.Matcher.__call__ (spacy/matcher.cpp:8519)
   Exception: Error selecting action in matcher
   

   How do I go from here? Seems like there's no debug logs available.
7. sadovnychyi commented on Oct 28, 2016

   

   sadovnychyi

   on Oct 28, 2016

   ContributorAuthor

   More actions

   Ok, got it. Hope you don't mind if I'll leave it here.

   import spacy
   import spacy.matcher
   
   nlp = spacy.load('en', parser=False, entity=False)
   matcher = spacy.matcher.Matcher(nlp.vocab)
   content = u'''a b; c'''
   matcher.add(entity_key='1', label='TEST', attrs={}, specs=[[]])
   matcher(nlp(content))

   ->

   Traceback (most recent call last): 
     File "word2vec/matcher_bla.py", line 8, in <module>
       matcher(nlp(content))
     File "spacy/matcher.pyx", line 315, in spacy.matcher.Matcher.__call__ (spacy/matcher.cpp:8519)
   Exception: Error selecting action in matcher
   

   Caused by empty specs. While I understand that this is a mistake in my data it's better to check this when entity is being added.
8. savkov commented on Nov 10, 2016

   

   savkov

   on Nov 10, 2016

   Contributor

   More actions

   I had that last week but it disappeared when I updated the data. I was suspecting empty pattern/key caused it. Thanks for the explanation!
9. lock commented on May 9, 2018

   

   lockBot

   on May 9, 2018

   More actions

   This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
10. lock

    locked as resolved and limited conversation to collaborators on May 9, 2018