VM

threading problems - arithmetic error - revno 1174

Bug #753637 reported by John Hein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Released
High
Uday Reddy

Bug Description

I made a virtual folder (using V S) of four messages

On the first C-t, I got:

vm-build-threads: Arithmetic error

On the second:

Generating summary... 0

On the third, it pegged the CPU for maybe 20 seconds and again:

Generating summary... 0

And the virtual folder was still sorted by 'physical-order'.

Exiting the virt folder and turning on debug-on-error gives:

Debugger entered--Lisp error: (arith-error)
  vm-build-reference-threads(([[#<marker at 1 in (INBOX.curr subject Creating Archives)> #<marker at 34 in (INBOX.curr subject Creating Archives)> #<marker $
  vm-build-threads(nil)
  vm-sort-messages("activity")
  vm-toggle-threads-display()
  call-interactively(vm-toggle-threads-display nil nil)

For another (single message) virt folder ...

Debugger entered--Lisp error: (arith-error)
  vm-build-reference-threads(([[#<marker at 1 in (INBOX.curr subject Opening Day Scrimmage rules)> #<marker at 34 in (INBOX.curr subject Opening Day Scrimma$
  vm-build-threads(nil)
  vm-sort-messages("activity")
  vm-toggle-threads-display()
  call-interactively(vm-toggle-threads-display nil nil)
  recursive-edit()
  byte-code("\306^P @\307=\203!^@\310\311\312\"\210\313\311!\211^ZA@)\242\314=\203!^@\310\315\312\"\210\316^K!\210\317 \210\320 !\210\f\203d^@\321ed\"^MV\20$
  debug(error (arith-error))
  vm-build-reference-threads(([[#<marker in no buffer> #<marker in no buffer> #<marker in no buffer> #<marker in no buffer> #<marker in no buffer> #<marker $
  vm-build-threads(nil)
  vm-sort-messages("activity")
  vm-toggle-threads-display()
  call-interactively(vm-toggle-threads-display nil nil)

Tags: new threading
Revision history for this message
Uday Reddy (reddyuday) wrote : Re: [Bug 753637] [NEW] threading problems - arithmetic error - revno 1174

Yeah, sorry, there is indeed an arithmetic error in revision 1174,
which got fixed in 1175.

You can also use the latest revision, 1181, which seems to be working
ok.

Cheers,
Uday

Changed in vm:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Uday Reddy (reddyuday)
milestone: none → 8.2.0a
Revision history for this message
John Hein (xpqheqdvq4) wrote :

I'm now using 1181 and the reported problem is gone.

Uday Reddy (reddyuday)
tags: added: 8.2
Uday Reddy (reddyuday)
tags: added: new
removed: 8.2
Uday Reddy (reddyuday)
Changed in vm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.