ConcurrencyError: Detected invalid array contents due to unsynchronized modifications with concurrent users

Open
#4 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
observability

Research direction

Start by reading trashed/instruments/ruby_gc_profiler.rb and trashed/meter.rb, following the stacktrace through measure, start, and instrument!. Reproduce the ConcurrencyError with concurrent users and inspect the timer and profiler state involved; done means the reported invalid array contents error no longer occurs under that workload.

Written by the indexing model from the issue text.

Description

Stacktrace (most recent call first):

  org/jruby/RubyArray.java:1613:in `each'
  org/jruby/RubyEnumerable.java:977:in `each_with_index'
  trashed/instruments/ruby_gc_profiler.rb:12:in `measure'
    timings[:"#{captured}.time"] ||= 1000 * GC::Profiler.total_time
  trashed/instruments/ruby_gc_profiler.rb:7:in `start'
    measure state, timings, gauges, :OOBGC
  trashed/meter.rb:31:in `instrument!'
    @timers.each { |i| i.start state, timings, gauges }
Dominant language
Ruby
Stars
193
Forks
23
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from basecamp/trashed

All issues in basecamp/trashed

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.