This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | IllegalArgumentException: Cannot decrease processed workunit count (500) to lower value than before (1000) | ||
|---|---|---|---|
| Product: | java | Reporter: | facilityderek <facilityderek> |
| Component: | FindBugs | Assignee: | Jan Lahoda <jlahoda> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alexvsimon, everflux, gtzabari, itreppert, jlahoda, lhochet, MackSix, mmirilovic, sentrox, theanuradha, zdenek.rod |
| Priority: | P3 | ||
| Version: | 7.2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | 190135 |
| Attachments: |
stacktrace
stacktrace |
||
|
Description
facilityderek
2012-06-27 08:44:36 UTC
Created attachment 121433 [details]
stacktrace
Seems to be related to Find Bugs too. Reassigning. Most of the reports are from version 1.13 of the findbugs integration module, which does not contain fix for bug #213803. One from version 1.14: http://statistics.netbeans.org/exceptions/exception.do?id=599815 Unclear how that could happen. This bug already has 20 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=190135 Honza, please re-evaluate. Thanks in advance. From what I can tell, there appear to be about three reports for findbugs version 1.14: http://statistics.netbeans.org/exceptions/exception.do?id=599815 http://statistics.netbeans.org/exceptions/exception.do?id=605528 http://statistics.netbeans.org/exceptions/exception.do?id=654364 I still do not see how this could happen, so a way to reproduce would be very welcome. Without that the most I can do is to suppress the exception, which would basically mean we will never find the root cause. I also ran into this - once (in 7.3). I do something like
final ProgressHandle handle = ProgressHandleFactory.createHandle ( "xx" );
final AtomicInteger progressCounter = new AtomicInteger ( 0 );
And then do things in many threads, each calling
handle.progress ( progressCounter.incrementAndGet () );
when done. And one of them generated an exception.
Maybe change the API to have a
handle.increment ()
type function or don't check for lower values, simply use the max of the new value and the current max in
handle.progress ( value );
Regards
MG
Created attachment 134443 [details]
stacktrace
Run Inspect, All Analyzers on PHP project causes this.
(In reply to comment #6) <snip> > I still do not see how this could happen, so a way to reproduce would be very > welcome. Without that the most I can do is to suppress the exception, which > would basically mean we will never find the root cause. <snip> It's reproducible for me. 1. Create new default PHP project 2. Run Source>>Inspect with "All Analyzers" on the PHP project. This happens every time. Product Version: NetBeans IDE 7.3 (Build 201302132200) Java: 1.7.0_11; Java HotSpot(TM) 64-Bit Server VM 23.6-b04 Runtime: Java(TM) SE Runtime Environment 1.7.0_11-b21 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) Product Version: NetBeans IDE Dev (Build 201305102300) Java: 1.7.0_21; Java HotSpot(TM) 64-Bit Server VM 23.21-b01 Runtime: Java(TM) SE Runtime Environment 1.7.0_21-b11 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) Integrated into 'main-golden', will be available in build *201305281155* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/f51564646454 User: Jan Lahoda <jlahoda@netbeans.org> Log: #214851: support for zero sized work units. |