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

Search crash #1013

Open
1 task done
Kiliggggg opened this issue Nov 9, 2024 · 3 comments
Open
1 task done

Search crash #1013

Kiliggggg opened this issue Nov 9, 2024 · 3 comments
Labels

Comments

@Kiliggggg
Copy link

Kiliggggg commented Nov 9, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

It's sporadic. We haven't found a pattern yet.
Error:
Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.IO.UnmanagedMemoryAccessor.ReadByte(Int64)
at Lucene.Net.Store.DataInput.ReadVInt32()
at Lucene.Net.Codecs.Lucene41.Lucene41PostingsReader.ReadVInt32Block(Lucene.Net.Store.IndexInput, Int32[], Int32[], Int32, Boolean)
at Lucene.Net.Codecs.Lucene41.Lucene41PostingsReader+BlockDocsEnum.RefillDocs()
at Lucene.Net.Codecs.Lucene41.Lucene41PostingsReader+BlockDocsEnum.NextDoc()
at Lucene.Net.Search.Weight+DefaultBulkScorer.ScoreAll(Lucene.Net.Search.ICollector, Lucene.Net.Search.Scorer)
at Lucene.Net.Search.IndexSearcher.Search(System.Collections.Generic.IList`1<Lucene.Net.Index.AtomicReaderContext>, Lucene.Net.Search.Weight, Lucene.Net.Search.ICollector)
at Lucene.Net.Search.IndexSearcher.Search(Lucene.Net.Search.Weight, Lucene.Net.Search.ScoreDoc, Int32)
at EDiscovery.Core.Search.Searcher.Search(EDiscovery.Core.Query.Query, EDiscovery.Core.Query.Sort, EDiscovery.Core.Query.ScoreDoc, Int32)

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

Lucene.NET Version

4.8.0-beta00016

.NET Version

.NET 8

Operating System

Linux

Anything else?

No response

@NightOwl888
Copy link
Contributor

Could you try upgrading to 4.8.0-beta00017 to see if it still happens?

@Kiliggggg
Copy link
Author

Could you try upgrading to 4.8.0-beta00017 to see if it still happens?

Got it, I will try it then update the result, thank you.

@Kiliggggg
Copy link
Author

We are using the 4.8.0-beta00017 but the error still exists.

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

No branches or pull requests

2 participants