ArrayBufferView.sort Broken (I think!!) #4203
Replies: 1 comment
-
Posted at 2014-11-01 by @gfwilliams I'm afraid this definitely looks like a bug! I'll try and sort it out next week. Thanks for coming up with such a clear demonstration of it :) Posted at 2014-11-01 by DaveNI That would be great - I appreciate you must be extremely busy with project Pico! I only have about 40 elements so I am calling a simple bubble sort routine to work around the issue. Posted at 2014-11-01 by @gfwilliams I just looked into this and it appears to be some issue with ArrayBuffers where the element size is >1 byte - so normal Uint8Array works (probably why it got through testing). For ~40 elements you could use a normal array for now, but hopefully I'll be able to get this fixed quite soon. Posted at 2014-11-01 by @gfwilliams Ok, I know what the issue is, however it turns out that back in March I merged in a pull request where someone had modified the Makefile and had disabled all the debug checks in the code. So on Monday I've now got to go through and fix all the issues that should have been detected since March but weren't. On the plus side, it should be super-reliable after all that! Posted at 2014-11-03 by @gfwilliams Hi Dave, I just fixed this - it'll be in the 1v71 release |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2014-10-31 by DaveNI
I have refactored some code to save memory using Typed Arrays and have come in to a problem which I have managed to replicate using the following code:
I get the following Output for the second console.log (the first is as expected):
As you can see its a bit of a mess - some values missing, others repeated.
I haven't exceeded the maximum value for a Uint32 ( 4,294,967,295).
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions