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

SIGSEGV while using LurchTable in Xamarin.iOS project #3

Closed
rohitkumbhar opened this issue Feb 21, 2020 · 3 comments
Closed

SIGSEGV while using LurchTable in Xamarin.iOS project #3

rohitkumbhar opened this issue Feb 21, 2020 · 3 comments

Comments

@rohitkumbhar
Copy link

Hi! Ive been attempting to use J2N LurchTable in an iOS app developed using Xamarin. The app crashes with a SIGSEGV on any iOS device.
Error: J2N.Collections.Concurrent.AddInfo``2:CreateValue <0x0006c>
However it does work as expected in the iOS simulator. I am guessing this might be a x64 (Simulator) vs ARM64 (device) issue but I can't see any reason from the source code.

J2N version: 2.0.0-beta-0002

Attached:

The original crash was while trying to using DirectoryTaxonomyReader from Lucene.Net project. However I have narrowed it down to the LurchTable class. J2N version 1.00-beta-0001 crashes the same way. The un-refactored LurchTable from Lucene.Net.Support crashes as well.

@NightOwl888
Copy link
Owner

Hi, is this still an issue with 2.0.0-beta-0012?

While it may not be related, in that release we added Xamarin Android tests and discovered and fixed an infinite recursion bug with ArrayEqualityComparer<T> due to incomplete generics support. The bug was so severe that Lucene.NET would not even run on Xamarin Android because much of the index reader and writer code uses it (not sure about Xamarin iOS, though).

My thought is that now that MAUI is just around the corner that we should probably just add an abstract factory to DirectoryTaxonomyWriter in Lucene.Net.Facet so you can inject your own cache implementation by subclassing LruDictionary<TKey, TValue> with whatever cache works on your platform. This would allow people to work around this until they can upgrade to MAUI which (hopefully) has fixed generics support. However, I find it odd that you are the only one who reported a crash after we changed the generics and in fact we had someone confirm it was working on a real iOS device (apache/lucenenet#273 (comment)).

@rohitkumbhar
Copy link
Author

Hi! Unfortunately I am not in a position to verify it. However I don't think this is an issue any more since the current plan is to move away from Xamarin.

@NightOwl888
Copy link
Owner

Great. I guess time has healed this one 😆.

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

No branches or pull requests

2 participants