yigit/android-priority-jobqueue

Crash that I can't explain

Open

#299 opened on Dec 29, 2016

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (3,406 stars) (403 forks)batch import
help wanted

Description

Hello,

I see the following crash for my app on crashlytics. Don't know in which situation it is reproducible or why it happens. Could you please assist? Stack trace below:

Fatal Exception: java.lang.IllegalStateException: Cannot set a Job from JobHolder after it is sealed. at com.birbit.android.jobqueue.Job.updateFromJobHolder(SourceFile:131) at com.birbit.android.jobqueue.JobHolder$Builder.build(SourceFile:419) at com.birbit.android.jobqueue.JobManagerThread.handleAddJob(SourceFile:131) at com.birbit.android.jobqueue.JobManagerThread.access$000(SourceFile:35) at com.birbit.android.jobqueue.JobManagerThread$1.handleMessage(SourceFile:225) at com.birbit.android.jobqueue.messaging.PriorityMessageQueue.consume(SourceFile:39) at com.birbit.android.jobqueue.JobManagerThread.run(SourceFile:220) at java.lang.Thread.run(Thread.java:841)

Thank You, Dheer

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
JavaAndroid developmentUnderstanding of JobQueue library internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the crash by examining the stack trace in Job.updateFromJobHolder (line 131) and JobHolder.Builder.build (line 419) from the library source. Determine under what conditions a JobHolder can be sealed and then modified. Look for any missing checks or race conditions in the JobManagerThread. Since the issue lacks a reproduction case, attempt to create a minimal Android app that triggers the error, possibly by manipulating job states. Check if there are any recent commits or discussions in the repository that address this issue.