Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Issues
  • #313

Closed
Open
Created Apr 16, 2019 by Mark Brooker@walkjiveflyMaintainer

crownd crashes at random with assertion failure

Summary

4 times in the last 4 days a crownd wallet has crashed. It appears to happen while writing a message in the debug.log - there's a timestamp but no message

Steps to reproduce

Unknown

Expected behavior

wallet should run without crashing

Problematic behavior

assertion failure and crash

Crown-core environment info

Ubuntu 16.04

Crown-core application info

Crown version v0.13.2.0-12a897ba (2019-04-13 23:18:37 +0400)

Relevant logs, dumps and/or screenshots

No coredump yet, hopefully next time!

crown@Crown-Testnet:~/explorer$ crownd: /home/gitlab-runner/builds/Z452ydcR/0/crown/crown-core/depends/x86_64-unknown-linux-gnu/include/boost/unordered/detail/implementation.hpp:2933: void boost::unordered::detail::table<Types>::clear() [with Types = boost::unordered::detail::map<std::allocator<std::pair<const uint256, CCoinsCacheEntry> >, uint256, CCoinsCacheEntry, CCoinsKeyHasher, std::equal_to<uint256> >]: Assertion `!size_' failed.

debug.log ends with

2019-04-16 02:56:01 ProcessNewBlock : ACCEPTED
2019-04-16 02:56:01 ProcessNewBlock : ACCEPTED
2019-04-16 02:57:49

Previous occurrences at

2019-04-15 06:07:01 ProcessNewBlock : ACCEPTED
2019-04-15 09:23:12

and with Crown version v0.13.0.0-2324299d

2019-04-12 13:59:01 snw - invalid message - Unknown Systemnode c89d1d5064404224ad1269496827adc58e4ee63ab04fb98944b7866fa206ca8d-0
2019-04-12 14:02:26

and

2019-04-12 02:26:01 ProcessNewBlock : ACCEPTED
2019-04-12 06:53:26

Drop full logs & dumps here: https://nextcloud.crown.tech/nextcloud/s/znd8HiiAsRX3C6B

Possible fixes

Looks like a boost problem and not one that Google knows about, triggered by something in coins.cpp

/cc @artem

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking