Live data from Hacker News

GPT-3.5 crashes when it thinks about useRalativeImagePath too much

iter.ca

121–130 of 164 posts

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#122

Earlier quoted context omitted.

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

Can't wait for people to wreack havoc by shouting a kill word at the inevitable smart car everyone will have in the future.

More realistically it'll be a "kill image". Put it on your bumper and the car behind yours' level-2 self driving implodes.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#123
post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Using /r/counting to train an LLM is hilarious.

I mean, you need to teach a LLM the concept of sequential numbers somehow.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#124
post #39

Earlier quoted context omitted.

As someone else who has regular ocular migraines, this causes absolutely no anxiety for me. I can kind of see the resemblance but it's pretty obviously not one. And if it was, is it really so bad getting them? For me it's just a weird optical effect that passes... I really don't think anyone needs to go out of their way to accommodate my quirk.

For me they are. Mine start -exactly- like this, seeing colors on white that aren't there. Then progresses to losing vision in your center focus, making you read from a periphry. Then moves to what I can only describe as a mountain dew colored wiggling lightning bolt, with extreme light sensitivity and sometimes dull headache. Lasts anywhere from 30m to 90m, usually. I'm only slightly trying to play a 'trigger warnin…

Good thing it doesnt actually trigger it I guess.

Sounds like mine are milder they only last around 5-10mins and I just get the central ring - looks like I stared at a donut shaped lightbulb for too long, and almost never associate with a headache (but sometimes with a hard to describe wooziness).

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#125
post #39

Earlier quoted context omitted.

As someone else who has regular ocular migraines, this causes absolutely no anxiety for me. I can kind of see the resemblance but it's pretty obviously not one. And if it was, is it really so bad getting them? For me it's just a weird optical effect that passes... I really don't think anyone needs to go out of their way to accommodate my quirk.

I have infrequent migraines and this scared the ever living fuck out of me. Mine are of the "wouldn't you rather be dead?" variety when it comes to headache and vomiting, though.

Ocular migraines are different from "real" migraines as they dont have the terrible headache that comes with. Just the optical effects.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#127
post #115

I know it's not good faith to complain about a site design rather than it's content, but please don't do whatever this is to your background. As someone with regular ocular migraines, opening this on mobile made my anxiety shoot straight up thinking I'm having another.

Author here, I removed the background.

Thank you!

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#129
post #17

Earlier quoted context omitted.

Aren’t there only 2^16 tokens? Seems easy to test for all of them, but I might just not understand the tokenizer.

You're right, here's a list of all GPT-3.5 and GPT-4 glitch tokens (and it features the token above, too, so I guess I was wrong to assume it's new): https://www.lesswrong.com/posts/kmWrwtGE9B9hpbgRT/a-search-f...

Something about these makes them incredibly funny to read.
Post reply on HN