Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle null raw_choice - fixes #235 #246

Closed
wants to merge 1 commit into from

Conversation

tfmorris
Copy link
Contributor

@tfmorris tfmorris commented Mar 1, 2016

I'm not sure this is the best fix for the issue, but it does provide a workaround while someone works out what the root cause is and where it should really be fixed.

@@ -795,6 +795,8 @@ static int SelectBestWords(double rating_ratio,
bool debug,
PointerVector<WERD_RES>* new_words,
PointerVector<WERD_RES>* best_words) {


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the reason for empty lines?

@tfmorris
Copy link
Contributor Author

tfmorris commented Mar 2, 2016

I've cleaned up the cosmetic issues.

Any insight into what the root cause is? I'm not sure that this is more than a bandaid.

@zdenop
Copy link
Contributor

zdenop commented Mar 3, 2016

I am not sure if it is an good idea to return valid output (0.0) when tesseract did not produced certainty...
And as you mentioned: this patch does not solve root of problem. I suggest to keep it open for Ray investigation.

@Shreeshrii
Copy link
Collaborator

@theraysmith Will this PR help with the word getting dropped - #681

@amitdo
Copy link
Collaborator

amitdo commented Jan 25, 2018

It's not related at all to #681.

@amitdo
Copy link
Collaborator

amitdo commented Jan 25, 2018

You can try #1264 for #681.

@zdenop
Copy link
Contributor

zdenop commented Apr 20, 2018

Can somebody (@Shreeshrii ?) check if this is relevant for 4.0 (if it helps)?

@Shreeshrii
Copy link
Collaborator

I will request @stweil to review. Thanks.

@stweil
Copy link
Contributor

stweil commented Apr 20, 2018

Link to issue: #235.

@stweil
Copy link
Contributor

stweil commented Apr 20, 2018

I added the issue to the planning list and will have a look next week.

@zdenop
Copy link
Contributor

zdenop commented Sep 24, 2018

@tfmorris : do you have test case for this PR?

@zdenop zdenop closed this in f6fd9b3 Oct 13, 2018
@tfmorris
Copy link
Contributor Author

@zdenop Sorry for the delayed reply. I do not have a unit test for the PR. It's 2 1/2 year old, but from looking at the historical context, I'm guessing that I was able to reproduce the failure in #235 and manually tested using that test case.

Since the test case in #235 was tested and no longer crashes, I don't think this PR is needed.

@amitdo
Copy link
Collaborator

amitdo commented Oct 13, 2018

The segfault is gone, but the other part of the issue still exist with the 'tessdada' repo (but not with best / fast)

@amitdo
Copy link
Collaborator

amitdo commented Oct 13, 2018

In any case, patches that don't solve the root of the issue are problematic IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants