Trying to open a particular Realm DB file throws the following exception - "Upgrading from file format version 22 to 24 D:\a\realm-dotnet\realm-dotnet\wrappers\realm-core\src\realm/util/encrypted_file_mapping.hpp:180: [realm-core-14.5.1] Assertion failed: local_ndx < m_page_state.size() with (local_ndx, m_page_state.size(), size_t(addr), size_t(m_addr), m_page_shift) = [85, 1, 2331762327552, 2331762294784, 16] <backtrace not supported on this platform>"

[clement-ilango]

What happened?

Info: DB: 61583 Thread 48384: Upgrading from file format version 22 to 24
D:\a\realm-dotnet\realm-dotnet\wrappers\realm-core\src\realm/util/encrypted_file_mapping.hpp:180: [realm-core-14.5.1] Assertion failed: local_ndx < m_page_state.size() with (local_ndx, m_page_state.size(), size_t(addr), size_t(m_addr), m_page_shift) = [85, 1, 2331762327552, 2331762294784, 16]

Repro steps

Same as above.

Version

.NET FRAMEWORK 4.7.2

What Atlas Services are you using?

Local Database only

What type of application is this?

WPF

Client OS and version

Windows 10

Code snippets

        var config = new RealmConfiguration(fileName);
        config.SchemaVersion = 6;

        config.Schema = new[] {....}

        if (!string.IsNullOrEmpty(FileName) && File.Exists(FileName))
        {
            var hex = File.ReadAllText(FileName);
            byte[] bytes = Misc.HexToBytes(hex);
            config.Key = bytes;
        }
        else
        {
            var hex = "";
            if (Settings.Instance.AndroidMobile.KeyEnabledOrNot)
            {
                hex = Settings.Instance.AndroidMobile.Key;
                if (string.IsNullOrEmpty(hex))
                    throw new Exception(Resources.strPleaseProvideKey);
            }
            if (!string.IsNullOrEmpty(hex))
            {
                byte[] bytes = Misc.HexToBytes(hex);
                config.Key = bytes;
            }
        }

        using (var realm = Realm.GetInstance(config))
        {
              //Do some things with the opened Realm DB
        }

Stacktrace of the exception/crash you're getting

No response

Relevant log output

2024-05-01 23:47:31.993 Info: DB: 61583 Thread 48384: Upgrading from file format version 22 to 24
D:\a\realm-dotnet\realm-dotnet\wrappers\realm-core\src\realm/util/encrypted_file_mapping.hpp:180: [realm-core-14.5.1] Assertion failed: local_ndx < m_page_state.size() with (local_ndx, m_page_state.size(), size_t(addr), size_t(m_addr), m_page_shift) =  [85, 1, 2331762327552, 2331762294784, 16]
<backtrace not supported on this platform>

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RNET-1141

[nirinchev]

You haven't specified the version of the Realm SDK that you're using, but this appears to be a bug that was fixed in the latest version - can you try upgrading to confirm?

[nirinchev]

@ironage this appears to be similar to the encryption bug that you fixed, but continues to happen even with Core 14.6.1, which should contain the fix. Is there anything obvious from the stacktrace or something we can ask the reporter to try track it down?

[ironage]

Hi @clement-ilango the stack traces you provided show you are using a core version of v14.5.1, and the relevant fix is in v14.6.0. For the .Net SDK this is version 12.1.0 (2024-05-01) or later. Please try upgrading and let us know if this solves the issue. If not, please provide an updated stack trace, and send your Realm file with encryption key to realm-help@mongodb.com.

[ironage]

@clement-ilango apologies, I missed this part of your latest message:

D:\a\realm-dotnet\realm-dotnet\wrappers\realm-core\src\realm/util/encrypted_file_mapping.hpp:184: [realm-core-14.6.1] Assertion failed: local_ndx < m_page_state.size() with (local_ndx, m_page_state.size(), size_t(addr), size_t(m_addr), m_page_shift) =  [85, 1, 1549425541120, 1549425508352, 16]

Which indicates that you are still seeing this on the updated version. Could you please still send the file to the email in my message above so that we can reproduce this and track down the issue?

[ironage]

@clement-ilango sorry, but I am unable to find your attachment when you respond by email to this thread. As far as I can tell, it is a limitation of Github's issue response system. Would you be able to send the file to realm-help@mongodb.com ?

[clement-ilango]

I did that. From: James Stone ***@***.***> Sent: Thursday, May 2, 2024 2:28 PM To: realm/realm-dotnet ***@***.***> Cc: Ilango, Clement ***@***.***>; Mention ***@***.***> Subject: Re: [realm/realm-dotnet] Trying to open a particular Realm DB file throws the following exception - "Upgrading from file format version 22 to 24 D:\a\realm-dotnet\realm-dotnet\wrappers\realm-core\src\realm/util/encrypted_file_mapping.hpp:180: [realm-co... EXTERNAL EMAIL: Only click links or open attachments if you recognize the sender and know the content is safe.

[ironage]

@clement-ilango I have received the files. Thanks for your patience in this process, we will investigate.

[nirinchev]

@clement-ilango I've edited the ticket in Jira to remove the sensitive information. Can you please double check to confirm. If there's more content that needs to be removed, can you please reach out to me via email at nikola.irinchev@mongodb.com.

[ironage]

We have merged a fix, please try when the next release is available that includes Core v14.10.0

[clement-ilango]

Hi James, Thanks a lot for letting me know that. Thanks, Clement. From: James Stone ***@***.***> Sent: Monday, June 10, 2024 2:59 PM To: realm/realm-dotnet ***@***.***> Cc: Ilango, Clement ***@***.***>; Mention ***@***.***> Subject: Re: [realm/realm-dotnet] Trying to open a particular Realm DB file throws the following exception - "Upgrading from file format version 22 to 24 D:\a\realm-dotnet\realm-dotnet\wrappers\realm-core\src\realm/util/encrypted_file_mapping.hpp:180: [realm-co... EXTERNAL EMAIL: Only click links or open attachments if you recognize the sender and know the content is safe. We have merged a fix, please try when the next release is available that includes Core v14.10.0 — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/realm/realm-dotnet/issues/3592*issuecomment-2159377060__;Iw!!BBM_p3AAtQ!MGf0NRfe9mMfCfn8_tWcXEnxMQKoZ5Rrul0eWexHLA1PA8-aiFHzxybMKAP75rJ_5BCqNrYsnPGlfCxhzSZLGz4iaJbe$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BIHAHP2ZQUXHYGOTBEXSJTDZGYOTVAVCNFSM6AAAAABHCX5UWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGM3TOMBWGA__;!!BBM_p3AAtQ!MGf0NRfe9mMfCfn8_tWcXEnxMQKoZ5Rrul0eWexHLA1PA8-aiFHzxybMKAP75rJ_5BCqNrYsnPGlfCxhzSZLGzhsspx9$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[nirinchev]

Fixed in 12.3.0